Skip to main content
Glama

AI text translation into 180+ languages

text_translate
Read-only

AI translation of up to 8,000 characters into a target language given as an ISO 639-1 code or English name (with optional region or script, e.g. pt-BR, zh-Hant). Returns the translated text, detected source language, target language, character counts and a truncation flag. Machine translation by Anthropic Claude under a fixed Kit Rx prompt that asks it to keep formatting, numbers, URLs and names; may contain errors; not a certified translation. Price: $0.005 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged. AI-generated answer; a call with no arguments returns the stored example answer without a model call.

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>",
      "to": "<to>"
    },
    "name": "text_translate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget language: ISO 639-1 code (es, ja, zh, de) or English name (Spanish, Japanese), optionally with a region or script subtag (pt-BR, zh-Hant, es-419).
fromNoSource language in the same forms as to. Detected automatically when omitted.
textYesText to translate, up to 8000 characters (URL-encoded in the query string). Line breaks and Markdown are preserved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint it discloses billing ($0.005 per successful call, USDC via x402 v2), that failed or non-matching calls are free, that output includes detected source language, character counts and a truncation flag, and that results are machine-generated and not certified. The no-argument example-answer path is a behavior no annotation could convey.

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?

Purpose and limits are front-loaded, then returns, then cost, then quality caveats and the fallback path — a sensible ordering with no filler. The later sentences are dense but each carries distinct information (pricing, caveats, no-op behavior).

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

Completeness5/5

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

With no output schema, the description fully covers the return shape (translated text, detected source, target, character counts, truncation flag) and the quality/pricing context an agent needs before spending money. Nothing material is missing for a 3-parameter, 2-required tool.

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 100% and the schema already documents 'to', 'from' and 'text' with examples, so the description's restatement of ISO 639-1/English-name forms adds little. The one genuinely new detail, the 8,000-character cap and truncation behavior, is already implied by the schema's text description.

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 opening sentence gives a specific verb and resource ('AI translation ... into a target language') plus hard scope (up to 8,000 characters) and the accepted language-code forms. It is clearly distinct from the nearest sibling, text_summarize, without needing to name it.

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

Usage Guidelines4/5

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

It gives concrete call conditions: source language is auto-detected when omitted, and a no-argument call returns the stored example answer without a model call. It never explicitly says when to prefer this over a sibling like text_summarize, so it stops short of the top band.

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