Synthex Forge — x402 Paid Agent Services

Check Governance State

check_governance_state

Read-onlyIdempotent

FREE and ungated by design (the adoption entry point). use it rather than verify_governance_state for governance state specifically; an object with 9 fields including algorithm, checked_at.

Input Schema

Name	Required	Description
`amount`	Yes	Spend amount in USD. Must be >= 0 and <= 1e12. Values above the bound are rejected with 422: no governor cap could authorise them, and the value cannot be stored in the governance ledger.
`intent`	No	Must not be empty. The handler rejects an empty value with 400 `bad_request`.
`agent_id`	Yes	Must not be empty. The handler rejects an empty value with 400 `bad_request`.

Output Schema

Name	Required	Description
`kind`	No	The `kind` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`sha256`	No	The `sha256` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`checked_at`	No	The `checked_at` field of the response.
`public_key`	No	The `public_key` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`standard_version`	No	The `standard_version` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

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 / kind

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

addedOutput schema / properties / public_key

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

addedOutput schema / properties / sha256

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

addedOutput schema / properties / signed_over

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

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

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

AddedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior; the description adds that it is free and ungated and mentions the output shape. It does not discuss auth, rate limits, or error behavior, but those are less critical for this annotated read tool.

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

Conciseness5/5

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

It is a single compact sentence with no filler; the free/ungated note and sibling routing are front-loaded, and the return shape is appended efficiently.

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 rich annotations, a fully described input schema, and an output schema, the description covers the key routing and cost context. It could state the governance-state concept more explicitly, but little is missing for correct invocation.

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?

The input schema has 100% description coverage for all three fields, so the description adds no parameter semantics beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

It identifies the tool as the read for governance state and explicitly contrasts it with verify_governance_state; the mention of an object with 9 fields reinforces the purpose. However, it never states the core action in a standalone phrase like 'retrieve current governance state,' so a bit of inference from the name is required.

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 names the sibling alternative and the selection criterion ('for governance state specifically'), plus says it is free and ungated. It does not state when to use verify_governance_state instead or cover any exclusions or prerequisites.

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.