Synthex Forge — x402 Paid Agent Services

Convert Document

convert_document

Read-onlyIdempotent

Utils Doc Convert. use it rather than translate_document for document specifically; an object with 14 fields including chars, converted. $0.1 USDC.

Input Schema

Name	Required	Description	Default
`to`	No	The to this operation operates on. See the schema for its type and whether it is required.	json
`text`	No	The source text the operation operates on.

Output Schema

Name	Required	Description
`kind`	No	The `kind` field of the response.
`meta`	No	The `meta` field of the response.
`note`	No	A note on how the answer was produced.
`chars`	No	The `chars` field of the response.
`lines`	No	The `lines` field of the response.
`words`	No	The `words` field of the response.
`format`	No	The `format` field of the response.
`utility`	No	The `utility` field of the response.
`document`	No	The `document` field of the response.
`sections`	No	The `sections` field of the response.
`converted`	No	The `converted` field of the response.
`word_count`	No	The `word_count` field of the response.
`utility_result`	No	The `utility_result` field of the response.
`word_frequencies`	No	The `word_frequencies` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 31, 2026

addedOutput schema / properties / chars

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

addedOutput schema / properties / converted

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

addedOutput schema / properties / document

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

addedOutput schema / properties / format

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / lines

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

addedOutput schema / properties / meta

Added value: +{
+  "description": "The `meta` 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 / sections

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

removedOutput schema / properties / status

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

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"
+}

addedOutput schema / properties / word_count

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

addedOutput schema / properties / word_frequencies

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

addedOutput schema / properties / words

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

AddedOct 31, 2026

TDQS

B3.4/5.0

Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive, and closed-world behavior, so the description need not repeat safety semantics. It adds meaningful context by disclosing the cost ($0.1 USDC) and describing the output as an object with 14 fields including 'chars' and 'converted'.

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 description is short and contains no repeated filler, but it is structured as awkward sentence fragments with capitalization and punctuation issues. The alternative-tool guidance appears before the purpose is clear, so it is not well 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?

The tool has only two optional parameters, full schema coverage, annotations, and an output schema, so the description does not need to explain return values in depth. However, it still fails to clarify the core conversion behavior or the target-format meaning of `to`, leaving an important semantic gap.

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 both parameters and the baseline is 3. The description adds no meaning about the `to` or `text` parameters beyond what the schema provides.

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 phrase 'Utils Doc Convert' largely restates the tool name and never explicitly states what conversion it performs or between which formats. It does distinguish itself from `translate_document`, but the condition 'for document specifically' remains vague rather than defining a clear verb-and-resource 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?

The description explicitly names the alternative tool and says to use this one rather than `translate_document` for documents. That is useful routing guidance, though the condition 'for document specifically' is imprecise and no when-not-to-use case is given.

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.