Skip to main content
Glama

block_translation_update

Edit a translation (Slate JSON); it stays active and feeds TM.

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": {
      "translation_id": "<translation_id>",
      "translated_content": "<translated_content>"
    },
    "name": "block_translation_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
translation_idYes
translated_contentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description does carry some behavioral weight: it discloses that the translation remains active and that the edit propagates to translation memory, which is a real side effect an agent should know. It omits permissions, whether translated_content replaces or merges, and what an invalid payload does, leaving the mutation semantics incomplete.

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?

A single compact sentence with the resource and format hint front-loaded and no filler. It is efficient, though the parenthetical is cryptic enough that it barely counts as clarification.

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?

For an unannotated mutation tool with two required, undescribed parameters and no output schema, the description is far too thin. It never explains the identity parameter, the update semantics, or the result of the call, so an agent would be guessing on invocation.

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 coverage is 0%, so the description must compensate. The parenthetical 'Slate JSON' usefully hints at the shape of translated_content, but translation_id is entirely unexplained, and the format hint is too terse to guide construction of the nested array of objects.

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 ('Edit a translation') and adds a format note about Slate JSON, which is more than a restatement of the name. It does not, however, distinguish itself from the sibling block_update or explain how editing a translation differs from editing a block.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternative. 'It stays active and feeds TM' describes a side effect, not a condition for selecting this tool over block_update or document_update.

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