Synthex Forge — x402 Paid Agent Services

Verify Bureau Result

verify_bureau_result

Read-onlyIdempotent

independently verify a Bureau preflight report's Ed25519 signature. use it rather than verify_bureau_anchor for bureau result, not bureau anchor; an object with 8 fields including detail, hash_valid.

Input Schema

Name	Required	Description	Default
`report`	Yes	Must contain at least one property. The handler rejects an empty object with 400 `bad_request`.

Output Schema

Name	Required	Description
`valid`	Yes	Whether the artifact verified.
`detail`	Yes	Human-readable explanation of the verdict.
`hash_valid`	No	The `hash_valid` field of the response.
`verified_at`	No	The `verified_at` field of the response.
`signature_valid`	No	The `signature_valid` field of the response.
`public_key_known`	No	The `public_key_known` field of the response.
`standard_version`	No	The `standard_version` field of the response.
`recomputed_sha256`	No	The `recomputed_sha256` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 31, 2026

addedOutput schema / properties / detail

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

addedOutput schema / properties / hash_valid

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

addedOutput schema / properties / public_key_known

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

addedOutput schema / properties / standard_version

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

Added value: +[
+  "detail",
+  "valid"
+]

AddedOct 31, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds that verification is independent and mentions an object with 8 fields including `detail` and `hash_valid`, which gives useful context about the verification result. It does not discuss failure modes, but the annotations and output schema carry much of that burden.

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?

Very short and front-loaded with the core action, then the sibling distinction. The phrase 'an object with 8 fields including detail, hash_valid' is slightly ambiguous about whether it refers to input or output, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists and annotations cover safety behavior, the description provides exactly what is needed: what to verify, which sibling to avoid, and a hint at the result shape. Nothing essential for correct invocation is missing.

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 coverage is 100%, and the schema itself explains that `report` must contain at least one property and rejects empty objects with 400 `bad_request`. The description does not add parameter-level semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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?

States a specific verb (verify), resource (Bureau preflight report), and cryptographic mechanism (Ed25519 signature). It explicitly distinguishes itself from the sibling verify_bureau_anchor, so an agent can select it without opening either 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?

Explicitly says to use this rather than `verify_bureau_anchor` for a bureau result, not a bureau anchor. This gives a clear alternative and the condition that selects it.

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.