Skip to main content
Glama

AutoTasker Hub — China Social Data API

translate_text

Free text translation via MyMemory (en->zh, zh->en, ja->en, ...). $0.01 USDC.

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": {
      "text": "<text>"
    },
    "name": "translate_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNozh-CN
fromNoen
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It usefully discloses the provider (MyMemory) and that each call costs $0.01 USDC — a material behavioral trait — but omits rate limits, character caps, accuracy caveats, and return format.

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?

Two terse fragments with zero padding and the core purpose front-loaded. The telegraphic style and trailing '...' sacrifice a little precision for brevity, but nothing is redundant.

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?

For a simple three-parameter tool with no output schema or annotations, the definition covers purpose, provider, and price but leaves an agent guessing about return shape and language-code coverage. Adequate, with clear gaps for a paid external call.

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%, so the description must compensate. The direction examples (en->zh, zh->en, ja->en) clarify that from/to are language codes, but the defaults (en, zh-CN) and the '...' wildcard of supported codes are left ambiguous, and the text parameter's constraints are unaddressed.

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 names a specific verb (translate) and resource (free text), plus the backing provider MyMemory and concrete language pairs. An agent knows exactly what the tool does; there is no sibling translation tool to differentiate from, so no routing gap remains.

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 example pairs hint at supported languages, but the description never states when to use this tool versus another, nor any exclusions (length limits, unsupported language pairs, batch vs single call). Usage must be inferred.

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.