tolgee-mcp

by ytarfa

Overview Schema Source Related Servers Discussions Admin

Python

Remote

set_translations

Set translation values for a key in a Tolgee project by mapping language tags to translated text.

Instructions

Set translation values for an existing key in a Tolgee project.

Args:
    project_id: The numeric ID of the project.
    key_name: The name of the existing key.
    translations: Dict mapping language tags to translation text values (e.g., {"en": "Hello", "fr": "Bonjour"}).

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": {
      "project_id": "<project_id>",
      "key_name": "<key_name>",
      "translations": "<translations>"
    },
    "name": "set_translations"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes
`key_name`	Yes
`translations`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only says 'set translation values', which implies mutation. It fails to disclose whether it overwrites or merges translations, error behavior for missing keys, idempotency, authorization needs, or rate limits.

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

Conciseness4/5

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

The description is concise with a two-sentence overview plus an args list. It is front-loaded with the purpose. Every sentence adds value, though the args section could be more structured.

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

Completeness2/5

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

Despite having an output schema (not shown), the description omits return value details, error conditions, and behavioral traits (merge vs overwrite). For a mutation tool, more context is needed to be fully self-contained.

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 coverage is 0% (no description in schema), so the description must compensate. It provides brief yet clear explanations for all three parameters, including an example for 'translations'. However, it lacks constraints like key existence validation or format specifics.

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 clearly states the action ('Set translation values') and target ('existing key in a Tolgee project'), using a specific verb+resource pattern. It implicitly distinguishes from sibling tools like 'create_key' or 'create_or_update_translations', but does not explicitly differentiate from the latter.

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

Usage Guidelines2/5

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

The description only states the basic context ('existing key') but provides no guidance on when to use this tool versus alternatives like 'create_or_update_translations', nor does it mention prerequisites or when not to use it.

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