Synthex Forge — x402 Paid Agent Services

Verify Governance State

verify_governance_state

Read-onlyIdempotent

independently verify a governor record's Ed25519 signature. use it rather than check_governance_state for governance state specifically; an object with 6 fields including detail, hash_valid.

Input Schema

Name	Required	Description	Default
`record`	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.
`signature_valid`	No	The `signature_valid` field of the response.
`public_key_known`	No	The `public_key_known` field of the response.
`recomputed_sha256`	No	The `recomputed_sha256` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 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"
+}

removedOutput schema / properties / status

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

addedOutput schema / properties / valid

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

A4.1/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, and the description adds the key behavioral trait beyond them: verification is independent and cryptographic (Ed25519), and the response carries `hash_valid` and `detail`. It does not say whether an invalid signature yields `hash_valid: false` or an error, which is the one behavior an agent most needs to plan around.

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 compact sentences with the action front-loaded ahead of the sibling routing. The trailing 'an object with 6 fields including detail, hash_valid' is mild redundancy given an output schema exists, but it does not bloat the entry.

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, full parameter coverage, and complete annotations, the definition covers what the agent needs to select and invoke it. The residual gap is failure semantics — what an agent should expect when the signature does not verify — which neither the description nor annotations address.

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 `record` property is documented, including the non-empty constraint and 400 `bad_request` behavior, so the baseline is 3. The description adds nothing about what the governor record must contain for signature verification to be meaningful (which fields are signed), leaving the schema to carry that load.

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 and resource — independently verify a governor record's Ed25519 signature — which is unambiguous about both action and cryptographic method. It also explicitly contrasts itself with `check_governance_state`, so the agent can distinguish it from the nearest sibling without reading 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative (`check_governance_state`) and gives the selecting condition: use this one for governance state specifically. That is clear routing guidance, though it doesn't spell out when verification is unnecessary (e.g., a trusted local record) or other prerequisites for calling 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.