Skip to main content
Glama

Machine translate keys

machine_translate
Destructive

Start machine translation for specified keys into target languages. Returns a batch job ID — use get_batch_job_status to poll for completion.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyNames": "<keyNames>",
      "targetLanguageTags": "<targetLanguageTags>"
    },
    "name": "machine_translate"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoOptional: branch name
keyNamesYesNames of keys to translate
namespaceNoOptional: namespace of the keys
projectIdNoID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project.
targetLanguageTagsYesLanguage tags to translate into (e.g. ['de', 'fr'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectId / description
      Previous value: -"ID of the project (required for PAT, auto-resolved for PAK)"New value: +"ID of the project. Can be left out when the credential is bound to one project: a project API key, or an OAuth token for one project."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds genuinely new behavior beyond the annotations: this is asynchronous and returns a batch job ID requiring polling. However, annotations declare destructiveHint=true, and the description never explains what is destroyed — presumably existing translations in the target languages get overwritten — nor what permissions or scope are needed. With annotations covering the safety profile, this is an adequate but incomplete disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and followed by the essential follow-up step. Nothing extraneous; every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The async job pattern is covered, which is the biggest missing piece for an agent, but with destructiveHint=true and no output schema, the definition should say what happens to existing translations and what the returned job ID implies about timing/failure. It is adequate for a five-parameter tool but leaves meaningful gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, including the note that projectId may be omitted when the credential is bound to a project, so the schema already carries parameter meaning. The description adds no clarification about keyNames, targetLanguageTags, namespace or branch handling, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('start machine translation for specified keys into target languages') and names the follow-up sibling get_batch_job_status. An agent can distinguish it from set_translation, get_translations and create_keys without consulting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to get_batch_job_status for polling, which is the key next step after invoking this tool. It does not say when to prefer machine translation over manual set_translation or how to handle keys that already have translations, so no true exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.