Skip to main content
Glama

textokit_translate_es

Translate to Spanish (Argentina): rioplatense voseo, any source language. 0.003 USDC per call (x402, Base), first 10 calls/day per IP free; an unpaid call returns the x402 payment requirements. Free sample: textokit_sample.

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": "textokit_translate_es"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to translate into Rioplatense Spanish; 1–6000…
toneNoOptional tone: formal, neutral or casual. Defaults to…
payment_signatureNoOptional, legacy: base64 x402 v2 payment payload. Preferred: params._meta["x402/payment"]. Never a private key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."New value: +"Optional, legacy: base64 x402 v2 payment payload. Preferred: params._meta[\"x402/payment\"]. Never a private key."
  2. Changed3 schema fields changed
    • changedInput schema / properties / payment_signature / description
      Previous value: -"Optional. Base64 x402 v2 payment payload signed by YOUR wallet for the requirements returned by a previous unpaid call. Never a private key."New value: +"Optional base64 x402 v2 payment payload for the requirements of a prior unpaid call. Never a private key."
    • changedInput schema / properties / text / description
      Previous value: -"Text to translate into Rioplatense Spanish; 1–6000 characters."New value: +"Text to translate into Rioplatense Spanish; 1–6000…"
    • changedInput schema / properties / tone / description
      Previous value: -"Optional tone: formal, neutral or casual. Defaults to neutral."New value: +"Optional tone: formal, neutral or casual. Defaults to…"
  3. First observed

TDQS

A4.2/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 well: it discloses the billing model (0.003 USDC per call via x402 on Base), the free quota (10 calls/day per IP), and the failure path (an unpaid call returns x402 payment requirements). It omits anything about the response shape or translation quality/latency characteristics.

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, dialect scope, price, quota, failure behavior and the free-sample pointer are packed into one front-loaded sentence plus a short pointer. No filler and nothing an agent needs buried late.

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 single-parameter translation call with no output schema and no annotations, the definition covers cost, limits, payment mechanics and the free alternative — the parts an agent cannot infer. The only gap is that it never says what comes back (translated string only, or with metadata), which is minor for this tool type.

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 the schema already documents text, the tone enum, and the payment_signature field including the 'never a private key' warning. The description adds no parameter detail beyond what the schema states, so the baseline of 3 applies.

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 plus resource ('Translate to Spanish (Argentina)') and further narrows it with 'rioplatense voseo, any source language', which pins the dialect variant and confirms source language is irrelevant. The function is clearly separable from siblings like textokit_source_bounded_summary or textokit_comparar_textos without opening any schema.

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?

Provides real operating context: cost per call, a free tier of 10 calls/day per IP, and an explicit alternative ('Free sample: textokit_sample'). It does not state when this tool is the wrong choice versus other textokit tools (e.g., summarization vs translation), so it stops short of full when/when-not 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.