Genesis402

Translate text

genesis402_translate

Translate text into major languages while preserving names, numbers and formatting; use for customer messages, documents, or UI strings.

Instructions

Paid ($0.006 USDC). Translate text into any major language while preserving names, numbers and formatting. Use for customer messages, documents or UI strings. To only identify a text's language call the language-detect endpoint through genesis402_call. Returns the translation as JSON. Payment: call once without payment_signature to get the exact price quote (nothing is charged or signed), then call again with the signed payment to receive the result and settlement details.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Target language as a name or ISO 639-1 code, e.g. 'Spanish' or 'es'.
`from`	No	Source language as a name or ISO code. Omit to auto-detect.
`text`	Yes	The text to translate, up to 8,000 characters.
`payment_signature`	No	Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Output Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes	QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.
`paid`	Yes	true only when a payment was settled for this call.
`price`	No	The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment.
`result`	No	PAID or FREE: the endpoint's JSON result.
`resource`	No	QUOTE_ONLY: the full URL of the paid resource.
`how_to_pay`	No	QUOTE_ONLY: how to sign and resend the call.
`settlement`	No	PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none.
`what_you_get`	No	QUOTE_ONLY: the rail's description of what the payment buys.
`payment_required_b64`	No	QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.
`also_accepted_networks`	No	QUOTE_ONLY: every network the 402 challenge accepts.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.6Oct 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true, but the description discloses the price ($0.006 USDC), the two-step quote-then-pay flow, that the first call charges nothing, and that the second call returns result plus settlement details. This is substantial behavioral context beyond the structured fields.

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?

Front-loads price and purpose, then routing, then payment mechanics. Every sentence earns its place, though the payment-flow sentence is dense enough that it could be tightened slightly.

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?

An output schema exists, so return details need not be enumerated; the description nonetheless notes the JSON result and settlement details, and fully covers the non-obvious payment protocol. Nothing an agent needs to call this correctly is missing.

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 all four parameters (including payment_signature and from/to semantics) are already documented in the schema. The description adds only a light gloss on target-language breadth; baseline 3 is correct when the schema carries the detail.

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+resource (translate text) plus the scope (any major language, preserving names/numbers/formatting). It also names the sibling it is not (language-detect via genesis402_call), letting an agent distinguish it without opening a schema.

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

Usage Guidelines5/5

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

Gives concrete use cases (customer messages, documents, UI strings) and an explicit alternative plus the condition that selects it ('To only identify a text's language call the language-detect endpoint'). Nothing is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.