Skip to main content
Glama

Set translation

set_translation
Destructive

Set or update translations for a key in one or more languages. The key must already exist — use create_keys to create it first.

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": {
      "keyName": "<keyName>",
      "translations": "<translations>"
    },
    "name": "set_translation"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoOptional: branch name
keyNameYesThe translation key name
namespaceNoOptional: namespace of the key
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.
translationsYesTranslations as {languageTag: text} map (e.g. {"en": "Hello", "de": "Hallo"})

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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write/overwrite risk is signaled structurally. The description adds the key-existence prerequisite but never states whether existing translations for the listed languages are overwritten or merged, which is the key behavioral question for a 'set' operation on a destructive tool.

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, zero waste, with the action stated first and the prerequisite second. Nothing is repeated from the title or schema.

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

Completeness4/5

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

For a five-parameter mutation with full schema coverage and no output schema, the definition covers the essential precondition. The remaining gap — overwrite/merge behavior for already-existing translations — is the one thing an agent would still need before calling it confidently.

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%, so all five parameters are documented in the schema itself, including the {languageTag: text} map format and the projectId fallback rule. The description only echoes the multi-language nature of the translations map and adds no semantics for branch or namespace beyond what the schema already says.

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

Purpose4/5

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

States a specific verb ('Set or update') and resource ('translations for a key'), plus scope ('one or more languages'). It does not explicitly distinguish itself from get_translations or machine_translate, though the create_keys cross-reference does anchor it against one sibling.

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?

Gives a clear precondition with an explicit alternative: the key must already exist and create_keys must be used first. No guidance on when to set versus machine_translate, or how branch/namespace selection affects targeting.

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.