Skip to main content
Glama

Tolca: business verification (KYB)

translate

translate
Read-onlyIdempotent

Translate between French (incl. Quebec French) and English. Input: text, target ('fr' | 'en'), optional tone. Costs $0.04 USDC per call (x402 v2, Base or Solana). Send the HTTP header PAYMENT-SIGNATURE with your x402 payment, or call POST https://tolca.tonbot.ca/v1/translate with an x402 client.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to translate (up to 40,000 characters)
toneNoTone of the translation: neutral, formal, casual or quebec (Québec French)
targetYesTarget language: fr (French) or en (English)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / target / description
      Added value: +"Target language: fr (French) or en (English)"
    • addedInput schema / properties / text / description
      Added value: +"Text to translate (up to 40,000 characters)"
    • addedInput schema / properties / tone / description
      Added value: +"Tone of the translation: neutral, formal, casual or quebec (Québec French)"
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations declare read-only, idempotent, non-destructive, open-world, but the description adds material behavior the annotations cannot convey: per-call pricing ($0.04 USDC), payment protocol (x402 v2), supported chains (Base or Solana), the exact header name, and a fallback HTTP endpoint. Payment/authentication requirements are the key hidden behavior here and it discloses them fully.

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?

Three tight sentences, front-loaded with the language scope before the operational payment details. The 'Input: text, target, optional tone' clause largely duplicates the schema and is the only expendable sentence.

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 three-parameter tool with no output schema, the definition covers purpose, constraints, and the non-obvious payment gate. It stops short of stating what is returned (translated string) or what happens on payment failure/insufficient funds, which would matter for an agent orchestrating paid calls.

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 enum values and length limit are already documented in the schema. The description restates text/target/tone and adds only the parenthetical that 'quebec' tone relates to Quebec French, which is a marginal addition. Baseline 3 applies.

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?

States a specific verb and resource (translate text) plus the constrained language pair, French (including Quebec French) to English, which an agent can immediately act on. It does not name any sibling tool or explicitly distinguish itself from summarize/extract, but the directionality constraint makes the scope unambiguous.

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 real usage conditions: the call costs $0.04 USDC and requires an x402 payment via the PAYMENT-SIGNATURE header or an x402 client against the given endpoint. There is no explicit when-not-to-use or alternative-tool routing, so it stops short of a 5.

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.