Skip to main content
Glama

Get translations

get_translations
Read-only

Get translations for a specific key in a Tolgee project. Returns translations in all project languages, or only the specified languages if provided.

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>"
    },
    "name": "get_translations"
  }
}

Input Schema

NameRequiredDescriptionDefault
branchNoOptional: branch name
keyNameYesThe translation key name
languagesNoOptional: language tags to filter by (e.g. ['en', 'de']). If omitted, returns all languages.
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.

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

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful return-scope context (all languages vs. a filtered subset), but says nothing about how branch or namespace affect results, or about pagination or missing keys.

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 sentences, zero waste, and front-loaded with the core action. The return-scope clarification is placed immediately after the purpose statement.

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 no output schema, the description carries the burden of explaining returns, and it does so at a high level (translations across languages). It is nearly complete for a simple read tool, missing only edge-case behavior such as unknown keys or namespaces.

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 languages filter semantics and the projectId fallback. The description only echoes the languages filtering behavior, adding no meaning beyond the schema. Baseline 3 applies.

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 and resource ('Get translations for a specific key in a Tolgee project') and clarifies the return scope (all project languages, or a filtered subset). This distinguishes it reasonably from siblings like get_key (key metadata) or list_keys, though it does not name those siblings explicitly.

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?

Usage is implied by the description: fetch translations for a key, optionally narrowing by language. There is no explicit when-to-use versus get_key, list_keys, or search_keys, and no mention of prerequisites or when this is not appropriate.

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.