Synthex Forge — x402 Paid Agent Services

Verify Bureau Anchor

verify_bureau_anchor

Read-onlyIdempotent

independently assert that a corpus record is bound into the day's. use it rather than verify_bureau_result for bureau anchor, not bureau result; an object with 8 fields including checked_at, detail.

Input Schema

Name	Required	Description
`proof`	No	The proof this operation operates on. See the schema for its type and whether it is required.
`record`	Yes	Must contain at least one property. The handler rejects an empty object with 400 `bad_request`.
`merkle_root`	Yes	Must not be empty. The handler rejects an empty value with 400 `bad_request`.

Output Schema

Name	Required	Description
`detail`	Yes	Human-readable explanation of the verdict.
`reason`	No	Why the verdict was reached.
`included`	No	The `included` field of the response.
`leaf_hash`	No	The `leaf_hash` field of the response.
`recipe_id`	No	The `recipe_id` field of the response.
`checked_at`	No	The `checked_at` field of the response.
`expected_root`	No	The `expected_root` field of the response.
`recomputed_root_from_leaf`	No	The `recomputed_root_from_leaf` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 31, 2026

addedOutput schema / properties / checked_at

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / expected_root

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

addedOutput schema / properties / included

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

addedOutput schema / properties / leaf_hash

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

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / recipe_id

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

addedOutput schema / properties / recomputed_root_from_leaf

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

removedOutput schema / properties / status

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

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

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds only an output shape note ('an object with 8 fields including checked_at, detail'), which duplicates the existing output schema and says nothing about failure modes or what a failed assertion looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is a truncated fragment followed by a semicolon-chained run-on, and the return-value note is tacked on mid-sentence. It is short but poorly structured and grammatically incomplete rather than economical.

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 cover safety, the input schema is fully documented and an output schema exists, so the remaining burden is small. But the one thing only the description can supply — what anchor verification actually means here and what a positive vs. negative result signifies — is exactly what the broken sentence fails to deliver.

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% and each of record, merkle_root and proof already carries validation notes in the schema. The description contributes nothing about how record/proof relate to the merkle_root or what the proof array is expected to contain, so baseline 3 is appropriate.

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 verb 'independently assert' and the notion of a corpus record bound into 'the day's' is present, and it explicitly names the sibling it replaces (verify_bureau_result). However the core sentence is truncated — 'bound into the day's' never resolves to a merkle root/anchor — so the actual object of the assertion is left for the agent to infer.

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 gives an explicit routing rule: use this rather than `verify_bureau_result` for bureau anchor, not bureau result. That is a real when-to-use-vs-alternative statement, though it stops short of stating any preconditions or exclusions (e.g. what to do if no proof is available).

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.