Synthex Forge — x402 Paid Agent Services

Verify Status Body

verify_status_body

Read-onlyIdempotent

independently verify a /v1/status body you received. use it rather than verify_data_freshness for body, not freshness; an object with 7 fields including error, hash_valid.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`error`	No	The machine-readable error code, when the operation failed.
`valid`	Yes	Whether the artifact verified.
`hash_valid`	No	The `hash_valid` field of the response.
`verified_at`	No	The `verified_at` field of the response.
`verified_by`	No	The `verified_by` field of the response.
`signature_valid`	No	The `signature_valid` field of the response.
`recomputed_sha256`	No	The `recomputed_sha256` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 31, 2026

addedOutput schema / properties / error

Added value: +{
+  "description": "The machine-readable error code, when the operation failed.",
+  "type": "string"
+}

addedOutput schema / properties / hash_valid

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

addedOutput schema / properties / recomputed_sha256

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

addedOutput schema / properties / signature_valid

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

removedOutput schema / properties / status

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

addedOutput schema / properties / valid

Added value: +{
+  "description": "Whether the artifact verified.",
+  "type": "boolean"
+}

addedOutput schema / properties / verified_at

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

addedOutput schema / properties / verified_by

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

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

AddedOct 31, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description only needs to add context. It adds 'independently verify' and says the body is an object with 7 fields including error and hash_valid, but it does not explain verification outcomes or failure behavior.

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?

Two short sentences front-load the purpose and the alternative. The second sentence is somewhat compressed ('for body, not freshness'), but every phrase carries information.

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?

With an output schema, annotations, and a zero-parameter schema, the description covers purpose, the alternative, and expected body shape. It still leaves 'what verification checks' implicit, but not enough to block correct invocation.

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

Parameters4/5

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

The tool has no formal parameters, so the schema baseline is 4. The description adds that the object has seven fields, including error and hash_valid, but it does not enumerate all seven, so it does not reach 5.

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?

The description gives a specific verb ('independently verify') and a specific resource ('a /v1/status body you received'), and it distinguishes the tool from verify_data_freshness. An agent can identify the tool's purpose without opening another 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?

It explicitly says to use this tool rather than verify_data_freshness for body verification, not freshness. That names both the primary alternative and the condition for choosing this tool.

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.