jargon_translator_translate

Pack: jargon-translator · Endpoint: https://gateway.pipeworx.io/jargon-translator/mcp

Translate between corporate jargon and plain English. Specify direction (jargon→plain or plain→jargon) and tone (passive_aggressive, enthusiastic, defeated). Returns translation and interpretation tips.

Example call

Arguments

{
  "content": "We need to leverage our synergies and circle back on this to ideate some low-hanging fruit.",
  "direction": "corporate_to_english",
  "formality": "passive_aggressive"
}

curl

curl -X POST https://gateway.pipeworx.io/jargon-translator/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"jargon_translator_translate","arguments":{"content":"We need to leverage our synergies and circle back on this to ideate some low-hanging fruit.","direction":"corporate_to_english","formality":"passive_aggressive"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('jargon_translator_translate', {
  "content": "We need to leverage our synergies and circle back on this to ideate some low-hanging fruit.",
  "direction": "corporate_to_english",
  "formality": "passive_aggressive"
});

More examples

{
  "content": "This project failed because we didn't have enough money and people quit.",
  "direction": "english_to_corporate",
  "formality": "enthusiastic"
}

Response shape

Always returns: translation, interpretation

{
  "type": "object",
  "properties": {
    "translation": {
      "type": "string",
      "description": "The translated text"
    },
    "interpretation": {
      "type": "string",
      "description": "Interpretation tips for the translation"
    }
  },
  "required": [
    "translation",
    "interpretation"
  ]
}

Connect

Add this to your MCP client config, or use one-click install buttons:

{
  "mcpServers": {
    "jargon-translator": {
      "url": "https://gateway.pipeworx.io/jargon-translator/mcp"
    }
  }
}

See Getting Started for client-specific install steps.