Skip to main content
Glama

Set registry translation

set_registry_translation
Destructive

Write a person's translation of a term's definition, or of a claim's statement and title, into one language (PM-1373) — a new one, or the machine's corrected (get_registry_translations gives its words). Other sites then show it in that language with no «machine-translated» mark. Markdown and $…$ formulas as in the source. 'text' empty takes the person's translation off, and the machine's is shown again. Only for somebody who may write in the project and, for a term, open its source.

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": {
      "kind": "<kind>",
      "id": "<id>",
      "lang": "<lang>"
    },
    "name": "set_registry_translation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe term's id (list_terms) or the claim's (list_claims).
kindYesterm or claim.
langYesThe language, a two-letter code, e.g. 'en'.
textNoThe definition or the statement in that language. Empty removes the person's translation.
titleNoA claim's title in that language. Optional: none keeps the claim's own. A term has none — its word stays as it is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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, and the description usefully adds that an empty 'text' deletes the person's translation so the machine's is shown again, plus the exact authorization prerequisites and the external effect on other sites' rendering. What is missing is anything about the response, whether a failed permission check errors or silently no-ops, or whether writes are audited/reversible.

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

Conciseness3/5

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

Front-loaded with the verb and resource, but the prose is dense and parenthetical, and the issue reference (PM-1373) plus the '(get_registry_translations gives its words)' aside consume attention without helping the caller. The delete-vs-set rule is buried mid-paragraph rather than separated, which hurts scanability for a mutation tool.

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

Completeness5/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 no output schema, the description covers the essential surface: what is written, per kind, the removal path, formatting rules, authorization gates, and the downstream visibility effect. An agent has everything needed to call it correctly and to know when it should not.

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

Parameters4/5

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

Schema coverage is 100%, so a baseline of 3 applies, and the description still adds real meaning: markdown and $…$ formulas must follow the source formatting, empty 'text' has delete semantics rather than storing an empty string, and 'title' being absent keeps the claim's own title while terms have no title at all. It does not add format details for 'lang' beyond the two-letter example already in the schema.

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 (write) and resource (a person's translation of a term's definition or a claim's statement and title), and scopes it to one language. It cleanly distinguishes the term case from the claim case and names get_registry_translations as the reading counterpart, so an agent can tell these apart without opening a schema.

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 clear conditions: use it to supply a human translation so other sites render it without the «machine-translated» mark, and send empty 'text' to revert to the machine's words. It also names the write-permission requirement and the term-specific requirement of opening the term's source. It does not explicitly say to call get_registry_translations for read-only inspection, but it points at it as the source of the machine's words.

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.

Resources