tolgee-mcp

Overview Schema Source Related Servers Discussions Admin

get_translation_history

Retrieve the modification history of a specific translation to track changes over time. Use this to review edits and maintain version control for translations.

Instructions

Get the modification history of a specific translation.

Args:
    project_id: The numeric ID of the project.
    translation_id: The numeric ID of the translation.

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

Input Schema

Name	Required	Description	Default
`project_id`	Yes
`translation_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description must bear full burden. It only indicates a read operation but does not disclose any behavioral traits (e.g., rate limits, error handling, or what happens if the translation doesn't exist).

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 short and front-loaded with the purpose. Two sentences efficiently convey the core action and parameters, with no unnecessary words.

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

Completeness3/5

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

Given the tool's low complexity (2 required params, output schema exists), the description is minimally adequate. However, it would benefit from mentioning that it returns a history log and any prerequisites (e.g., existence of translation).

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

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate. It merely repeats parameter names and says they are 'numeric IDs', which is already in the schema (integer type). It adds little extra meaning.

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?

The description clearly states 'Get the modification history of a specific translation,' which specifies the verb and resource. It distinguishes from siblings like 'get_translations' by focusing on history.

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?

No guidance on when to use this tool versus alternatives such as 'get_translations' or 'set_translations'. The description lacks any when-to-use or when-not-to-use instructions.

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