Synthex Forge — x402 Paid Agent Services

Verify Commerce Intent

verify_commerce_intent

Read-onlyIdempotent

Compare an instruction against a proposed order, field by field. use it rather than accept_task_deliverable for commerce intent, not task deliverable; an object with 25 fields including action, actual. $0.02 USDC.

Input Schema

Name	Required	Description
`order`	No	The ordering the operation applies.
`tolerance`	No	The tolerance this operation operates on. See the schema for its type and whether it is required.
`instruction`	No	The instruction this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`type`	No	The `type` field of the response.
`field`	No	The `field` field of the response.
`action`	No	The `action` field of the response.
`actual`	No	The `actual` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`status`	No	The status of the operation.
`coverage`	No	How much of the underlying corpus the answer is based on.
`expected`	No	The `expected` field of the response.
`problems`	No	The `problems` field of the response.
`severity`	No	The `severity` field of the response.
`agreement`	No	The `agreement` field of the response.
`exception`	No	The `exception` field of the response.
`dimensions`	No	The `dimensions` field of the response.
`compared_count`	No	The `compared_count` field of the response.
`mismatch_count`	No	The `mismatch_count` field of the response.
`verdict_meaning`	No	The `verdict_meaning` field of the response.
`unverified_count`	No	The `unverified_count` field of the response.
`tolerance_applied`	No	The `tolerance_applied` field of the response.
`uncompared_fields`	No	The `uncompared_fields` field of the response.
`actual_source_field`	No	The `actual_source_field` field of the response.
`advisory_mismatches`	No	The `advisory_mismatches` field of the response.
`blocking_mismatches`	No	The `blocking_mismatches` field of the response.
`material_mismatches`	No	The `material_mismatches` field of the response.
`expected_source_field`	No	The `expected_source_field` field of the response.
`unverified_material_dimensions`	No	The `unverified_material_dimensions` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed26 schema fields changedOct 31, 2026

addedOutput schema / properties / action

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

addedOutput schema / properties / actual

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

addedOutput schema / properties / actual_source_field

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

addedOutput schema / properties / advisory_mismatches

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

addedOutput schema / properties / agreement

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

addedOutput schema / properties / blocking_mismatches

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

addedOutput schema / properties / compared_count

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

addedOutput schema / properties / coverage

Added value: +{
+  "description": "How much of the underlying corpus the answer is based on.",
+  "type": "object"
+}

addedOutput schema / properties / detail

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

addedOutput schema / properties / dimensions

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

addedOutput schema / properties / exception

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

addedOutput schema / properties / expected

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

addedOutput schema / properties / expected_source_field

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

addedOutput schema / properties / field

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

addedOutput schema / properties / material_mismatches

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

addedOutput schema / properties / mismatch_count

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

addedOutput schema / properties / problems

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

addedOutput schema / properties / severity

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

addedOutput schema / properties / status / description
```
Added value: +"The status of the operation."
```

addedOutput schema / properties / tolerance_applied

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

addedOutput schema / properties / type

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

addedOutput schema / properties / uncompared_fields

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

addedOutput schema / properties / unverified_count

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

addedOutput schema / properties / unverified_material_dimensions

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

addedOutput schema / properties / verdict_meaning

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

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

AddedOct 31, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare this a safe, idempotent, read-only, closed-world operation, so the safety bar is pre-covered. The description adds genuinely additive context: the '$0.02 USDC' cost of invocation, which an agent cannot infer from annotations or schema. It doesn't elaborate on the comparison/verdict semantics, but the output schema exists to carry that.

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?

Short, but the flow is choppy: a lowercase 'use it' clause, a broken phrase ('an object with 25 fields including action, actual') with no clear referent, then a bare '$0.02 USDC'. It is compact but not cleanly front-loaded or grammatical, and the vague object clause does not clearly earn its place.

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 nested-object verification tool with an output schema and full annotation coverage, the description covers the essential decision info: purpose, alternative routing, and cost. Remaining gaps (tolerance semantics, what the 25-field object is) are minor rather than blocking.

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 itself documents all three params, making 3 the baseline. The 'an object with 25 fields including action, actual' hint loosely gestures at nested content but is ambiguous about which argument it describes, and 'tolerance' is not addressed at all.

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?

A specific verb+resource is given: 'Compare an instruction against a proposed order, field by field.' It explicitly distances itself from accept_task_deliverable for commerce intent. However the fragmented 'an object with 25 fields including action, actual' muddies the purpose since it is never made clear which object this refers to.

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?

Explicitly states 'use it rather than `accept_task_deliverable` for commerce intent, not task deliverable', naming the alternative and the condition that selects this tool over it. No positive when-to-use framing beyond the contrast, but the routing signal is clear.

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.