Synthex Forge — x402 Paid Agent Services

Translate Document

translate_document

Read-onlyIdempotent

Utils Translate Doc. use it rather than convert_document for document specifically; an object with 12 fields including User-Agent, engine. $0.1 USDC.

Input Schema

Name	Required	Description	Default
`src`	No	The src this operation operates on. See the schema for its type and whether it is required.	auto
`text`	No	The source text the operation operates on.
`target`	No	The target the operation acts on — a host, a service or an endpoint.	es

Output Schema

Name	Required	Description
`q`	No	The `q` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`engine`	No	The `engine` field of the response.
`utility`	No	The `utility` field of the response.
`langpair`	No	The `langpair` field of the response.
`original`	No	The `original` field of the response.
`User-Agent`	No	The `User-Agent` field of the response.
`translated`	No	The `translated` field of the response.
`utility_result`	No	The `utility_result` field of the response.
`source_language`	No	The `source_language` field of the response.
`target_language`	No	The `target_language` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 31, 2026

addedOutput schema / properties / User-Agent

Added value: +{
+  "description": "The `User-Agent` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / engine

Added value: +{
+  "description": "The `engine` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / kind

Added value: +{
+  "description": "The `kind` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / langpair

Added value: +{
+  "description": "The `langpair` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / original

Added value: +{
+  "description": "The `original` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / q

Added value: +{
+  "description": "The `q` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / source_language

Added value: +{
+  "description": "The `source_language` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / target_language

Added value: +{
+  "description": "The `target_language` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / translated

Added value: +{
+  "description": "The `translated` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / utility

Added value: +{
+  "description": "The `utility` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / utility_result

Added value: +{
+  "description": "The `utility_result` field of the response.",
+  "type": "object"
+}

AddedOct 31, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the useful non-annotation facts of cost ('$0.1 USDC') and an available engine, but the '12 fields including User-Agent' claim is unexplained and doesn't map to anything observable in the schema.

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?

It is short, but it is written as disconnected fragments ('Utils Translate Doc.') with the pricing and a stray field-count detail interleaved, so the most decision-relevant routing sentence is not cleanly front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present the description needn't explain return values, and annotations cover safety. But for a paid, idempotent translation call it omits format support and language-pair constraints, and the unexplained '12 fields/User-Agent' clause leaves an unresolved inconsistency an agent cannot act on.

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

Parameters2/5

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

Schema coverage is nominally 100%, but the schema descriptions are boilerplate ('The src this operation operates on...'), so the description is the only place real semantics could appear and it doesn't address src/text/target or auto-detection. Worse, 'an object with 12 fields' conflicts with the three-parameter schema, actively misleading the agent about input shape.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name/title plus 'Utils Translate Doc' imply a translation operation, but the description never cleanly states 'translates a document from src to target.' It does name a concrete sibling it should be preferred over (convert_document) for documents, which aids disambiguation, but the phrase 'an object with 12 fields including User-Agent, engine' muddies rather than clarifies the purpose.

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?

It explicitly routes the agent: 'use it rather than convert_document for document specifically,' which is a clear when-to-use statement against an actual alternative. There are no exclusions or preconditions (e.g., supported formats, language pairs), 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.

All Synthex Forge — x402 Paid Agent Services tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.