Synthex Forge — x402 Paid Agent Services

Clean Json Schema

clean_json_schema

Read-onlyIdempotent

Utils Schema Cleanup. use it rather than convert_document for json schema, not document; an object with 11 fields including cleaned, detail. $0.05 USDC.

Input Schema

Name	Required	Description	Default
`csv`	No	The csv this operation operates on. See the schema for its type and whether it is required.
`data`	No	The data this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`cleaned`	No	The `cleaned` field of the response.
`utility`	No	The `utility` field of the response.
`row_count`	No	The `row_count` field of the response.
`normalization`	No	The `normalization` field of the response.
`original_type`	No	The `original_type` field of the response.
`utility_result`	No	The `utility_result` field of the response.
`top_level_fields`	No	The `top_level_fields` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 31, 2026

addedOutput schema / properties / cleaned

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

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / kind

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

addedOutput schema / properties / normalization

Added value: +{
+  "description": "The `normalization` 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_type

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

addedOutput schema / properties / row_count

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

removedOutput schema / properties / status

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

addedOutput schema / properties / top_level_fields

Added value: +{
+  "description": "The `top_level_fields` 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"
+}

addedOutput schema / properties / value

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

addedOutput schema / required
```
Added value: +[
+  "detail"
+]
```

AddedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely new fact – a $0.05 USDC cost – which matters for a paid tool. The "object with 11 fields including cleaned, detail" restates return shape that the output schema already provides, so its added value is limited.

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, and the identity and the alternative are front-loaded, but the sentences are semicolon-spliced fragments that read as garbled ("for json schema, not document"). Compression has cost clarity here rather than earning it.

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?

Annotations and an output schema are present, and cost plus the sibling routing are disclosed, so the minimum is met. What is missing is the one thing an agent cannot get elsewhere: what transformation "cleanup" performs and therefore what input `data` should contain – the description leaves the core behavior undefined.

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% across the two optional parameters, so the schema is nominally the source of truth and baseline is 3. The description adds nothing about what `csv` or `data` mean for a schema-cleaning operation, and the schema's own text is generic boilerplate, leaving the distinction between the two parameters unexplained.

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?

"Utils Schema Cleanup" names the resource and an implicit verb (cleanup), and the phrase "use it rather than `convert_document` for json schema" tells an agent it operates on JSON schemas rather than documents. However, the description never states concretely what "cleaning" means (normalization? deduplication? validation?), so the purpose stays at a vague, category level.

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 names a specific sibling, `convert_document`, and states the discriminating condition: use this for json schema, not for document. That is a real routing rule an agent can act on. It stops short of saying when NOT to use this tool in any other sense (e.g., a schema that needs converting rather than cleaning), so it is not a full 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.