Skip to main content
Glama

APEX AI, LLM, Embeddings, OCR & Media

Text translate

text_translate
Read-onlyIdempotent

Translate text across 100 languages using Meta M2M100 1.2B AI. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to translate (1 to 8000 characters).
sourceNoOptional source ISO-639-1 language code (default en).
targetYesTarget ISO-639-1 language code (e.g. es, fr, de, pt, ja, zh, ko, ar, hi, uk, en).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (read-only, idempotent, non-destructive), so the description adds real behavioral value beyond them: cost ($0.001 per call), accepted payment rails (x402/USDC on Arc, Base or Solana; XNT on X1), and the two-step terms-then-payment handshake.

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?

Two sentences, front-loaded with purpose, then cost and the payment flow. Nothing is repeated from the schema or annotations, and each sentence carries necessary information.

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?

Covers the essentials for a paid translation tool: what it does, model, price, payment options, and the required call sequence. Return value is implied (translated text) and no output schema exists, but error cases and whether a payment payload is reusable are not stated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining how the `payment` parameter is used operationally (first call without it, second call with it), which the schema's 'signed x402 payment payload' line does not convey.

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?

States a specific verb (translate), resource (text), scope (100 languages) and underlying model (Meta M2M100 1.2B). No sibling in the list does translation, so the purpose is unambiguous without needing an explicit exclusion.

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?

Gives a concrete invocation protocol: call once without `payment` to receive terms, then call again with `payment`. That is clear when/how-to-use guidance, but it names no alternative tools or conditions for choosing not to use this one.

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.