Skip to main content
Glama

Get registry translations

get_registry_translations
Read-only

A term's definition or a claim's title and statement in other languages, as other sites are shown them (PM-1373): for each language a person wrote a translation in, or the thing's links carry or pages asked for — 'state' human (a person's, shown with no mark; 'outdated' true when the source was edited since), machine (the model's, shown marked «Machine-translated from …»; 'sourceLang' the language it was written in), pending (not translated yet: shown as written until the background pass gets to it) or original (already in that language) — with the words themselves, so a machine translation can be taken, corrected and saved with set_registry_translation. 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>"
    },
    "name": "get_registry_translations"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe term's id (list_terms) or the claim's (list_claims).
kindYesterm or claim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description's job is to add context, and it does: it enumerates the 'state' values (human/outdated/machine/pending/original), explains the outdated flag semantics, how machine output is marked, and what sourceLang means. It also discloses the permission gate. It stops short of stating pagination, ordering by language, or behavior when no translations exist, which keeps it off a 5.

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

Conciseness2/5

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

The whole definition is one sprawling sentence with nested parentheses, dash-separated asides, and an internal ticket reference (PM-1373) that carries no meaning for an agent. The purpose is front-loaded, but the enum semantics an agent actually needs are interleaved with prose rather than structured into a list, making it hard to scan.

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?

With only two required parameters, no output schema, and read-only annotations, the description carries the burden of explaining the returned shape — and it largely does, describing the state values, the machine-translation marker, sourceLang, and the translation text itself. Combined with the permission prerequisite, an agent has enough to call it and interpret the result; only empty-result and ordering behavior are unaddressed.

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% and both parameters are documented in the schema (term id via list_terms, claim id via list_claims; kind is term or claim), so the baseline is 3. The description adds only a mild cross-reference by tying 'a term, open its source' to the permission model; it adds no new syntax or format meaning for id or kind.

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?

The description does name the specific resource and scope: a term's definition or a claim's title and statement rendered in other languages, qualified as 'as other sites are shown them'. That is a real verb+resource statement rather than a restatement of the name. It is buried under an extremely dense parenthetical, so the core purpose takes effort to extract, but it is distinguishable from the sibling set, and it explicitly contrasts with set_registry_translation as the write path.

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

Usage Guidelines3/5

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

It gives one concrete prerequisite ('Only for somebody who may write in the project and, for a term, open its source') and points to set_registry_translation for the write-back case, which is useful routing. However, there is no guidance on when an agent should call this instead of reading the claim or term directly (e.g. get_claim), and no statement about when translations are not worth fetching.

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