Skip to main content
Glama

read_translation

Read-onlyIdempotent

Read a survey's language configuration, optional translatable answer-field keys for one question, or auto-translate job status.

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": {
      "survey_id": "<survey_id>"
    },
    "name": "read_translation"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoAuto-translate job UUID for status read-back
includeNoDefaults to languages only
survey_idYesSurvey UUID
question_idNoWhen set with include translatable_fields, lists answer-field keys for this question

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only a small amount beyond that, notably that job_id is used for status read-back and that question_id only applies with translatable_fields, both of which largely restate the schema.

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, front-loaded sentence that packs all three modes without filler. It is dense but readable; a short clause on the default include value would have made the mode selection fully self-contained.

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 four params at full schema coverage and an output schema present, return values need not be explained. The description covers all three read modes and the job_id dependency, leaving only minor gaps such as default behavior and what an empty language configuration looks like.

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 the baseline is 3. The description reinforces the conditional relationship between question_id and the translatable_fields include value but adds no format, ordering, or validation detail beyond what the schema already documents.

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 names a specific verb (Read) and resource (a survey's language configuration) and enumerates the three read modes: languages, translatable answer-field keys for one question, and auto-translate job status. This scope makes it clearly distinguishable from the sibling mutators edit_translation and delete_translation_language without opening any schema.

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?

The three modes are listed, so an agent can infer which include value it needs for each task, but there is no explicit guidance on when to choose each mode, nor any named alternative for changing translations. Usage is implied rather than stated.

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