Skip to main content
Glama

Web and geo tools (x402)

translate_text

$0.002 via x402: Translate one text (up to 2,000 characters) from a source language to a target language (ISO 639-1 codes such as en, es, fr, de, zh, ja, ar; 100 supported, list at https://translate.agentexchange.work/languages.json). Returns the translation, the languages and the character count. Pay 0.002 USDC through https://store.agentexchange.work/gw/translate/text?text=Hello+world&from=en&to=es Via the Agent

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

Input Schema

NameRequiredDescriptionDefault
toYestarget language code
fromYessource language code
textYestext
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key non-obvious traits: a paid x402 call costing 0.002 USDC, the payment URL, the required x_payment payload (schema), and a 2,000-character cap. It omits error/refund behavior and rate limits, but the payment/auth requirement — the most consequential trait here — is clearly surfaced.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is information-dense but front-loads the price ('$0.002 via x402') rather than the purpose, and packs purpose, limits, language guidance, return values and a long payment URL with embedded query params into one run-on block. Nothing is clearly wasteful, but structure and ordering could be improved.

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 simple 4-parameter tool with no output schema, the description covers purpose, input format, character limit, payment flow, and even the return fields (translation, languages, character count). Only failure modes and the distinction from translate_batch are left unaddressed.

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, but the terse schema descriptions ('text', 'target language code') are enriched by the description's ISO 639-1 format, concrete examples (en, es, fr, de, zh, ja, ar), the '100 supported' count, and the languages.json list URL. The payment path also clarifies how x_payment is used.

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 states a specific verb+resource ('Translate one text ... from a source language to a target language') and scopes it with a 2,000-character limit, which implicitly separates it from the batch sibling. It never names translate_batch explicitly, so sibling differentiation is inferred rather than stated.

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?

There is no when-to-use guidance or exclusion criteria: nothing says to pick translate_batch for multiple strings or translate_text for a single one. Operational facts (price, language codes) are given, but the agent gets no routing logic between alternatives.

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