Skip to main content
Glama

Translate parallel lines

translate_lines

Translate a list of lines between Chinese and English, keeping order and line count. Member feature — anonymous and free accounts get an auth prompt. For free usage, pass both sides yourself to create_bilingual_audio instead.

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": {
      "lines": "<lines>"
    },
    "name": "translate_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoSource language.zh
linesYesUp to 40 lines, one sentence each.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, it discloses the auth-prompt behavior for anonymous/free callers and the correctness guarantee that output order and line count are preserved, which an agent cannot infer from readOnlyHint=false/destructiveHint=false. It stops short of describing quota consumption, failure handling per line, or rate limits, so it is strong but not complete.

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?

Three short sentences, each carrying load: capability and invariant first, then access precondition, then the free-tier alternative. No filler or repetition, and the most decision-relevant constraint is front-loaded.

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?

For a two-parameter, non-destructive tool with full schema coverage and no output schema, the definition covers purpose, access gating, and the alternative route. It should ideally say what a returned list looks like when a line fails, but nothing essential to invoking it is missing.

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 'lines' and 'from' are already documented, including the 40-line cap that the description merely restates. The phrase 'between Chinese and English' loosely implies the from-enum drives direction, but adds no new format, length, or batching semantics beyond the schema.

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 concrete verb (translate) and resource (a list of lines), then constrains the domain to Chinese/English and guarantees order and line-count preservation. 'Lines' matches the actual parameter name, so an agent can map intent to this tool without opening the schema.

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

Usage Guidelines5/5

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

It states the membership precondition (anonymous and free accounts receive an auth prompt) and gives an explicit alternative with its trigger condition: free users should pass both sides themselves to create_bilingual_audio. That is a concrete when-to-use-this-vs-sibling rule rather than implied guidance.

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