Synthex Forge — x402 Paid Agent Services

Reserve Governance Budget

reserve_governance_budget

Destructive

Agent Spend Governor — ATOMIC reserved lease. use it rather than settle_governance_budget for governance budget specifically; an object with 19 fields including agent_id, algorithm. $0.02 USDC.

Input Schema

Name	Required	Description
`amount`	Yes	Spend amount in USD. Must be >= 0 and <= 1e12. Values above the bound are rejected with 422.
`intent`	Yes	The commercial intent the operation evaluates.
`agent_id`	Yes	The identifier of the agent the operation concerns.
`ttl_seconds`	No	How long the record stays valid, in seconds.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the operation succeeded.
`kind`	No	The `kind` field of the response.
`lease`	No	The `lease` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`reason`	No	Why the verdict was reached.
`sha256`	No	The `sha256` field of the response.
`verdict`	Yes	The decision this tool returned.
`agent_id`	No	The `agent_id` field of the response.
`enforced`	No	The `enforced` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`denied_at`	No	The `denied_at` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`public_key`	No	The `public_key` field of the response.
`settle_hint`	No	The `settle_hint` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`verify_hint`	No	The `verify_hint` field of the response.
`reserved_micro`	No	The `reserved_micro` field of the response.
`spent_today_micro`	No	The `spent_today_micro` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

addedOutput schema / properties / signature

Added value: +{
+  "description": "The Ed25519 signature over the evidence core, base64-encoded.",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "detail",
-  "ok",
-  "verdict"
-]New value: +[
+  "detail",
+  "ok",
+  "signature",
+  "verdict"
+]

Changed20 schema fields changedOct 31, 2026

addedOutput schema / properties / agent_id

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

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / denied_at

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

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / lease

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

addedOutput schema / properties / ok

Added value: +{
+  "description": "Whether the operation succeeded.",
+  "type": "boolean"
+}

addedOutput schema / properties / public_key

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

addedOutput schema / properties / reason

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

addedOutput schema / properties / reserved_micro

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

addedOutput schema / properties / settle_hint

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

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

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / verify_hint

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

addedOutput schema / required

Added value: +[
+  "detail",
+  "ok",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

C2.6/5.0

Behavior3/5

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

The annotations already declare this as destructive, non-idempotent, and not read-only. The description adds useful context with "ATOMIC" and a price of "$0.02 USDC," but it does not explain what exactly is locked or reserved, what the destructive hint implies, or how TTL expiry affects the reservation.

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 description is short but fragmented and poorly front-loaded. The irrelevant output-field detail ("an object with 19 fields including agent_id, algorithm") does not earn its place, especially since an output schema exists.

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

Completeness2/5

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

With an output schema and annotations present, the description still needs to clarify the reservation lifecycle, TTL behavior, and relationship to settlement or release tools. It omits these while spending space on output shape and a vague routing claim.

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%, so the schema already fully documents amount, intent, agent_id, and ttl_seconds. The description mentions agent_id but also mentions "algorithm," which is not an input parameter, and adds no meaningful input semantics beyond the schema.

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 description states a specific verb and resource ("reserve_governance_budget") and adds "ATOMIC reserved lease," which clarifies the operation. However, the phrase "an object with 19 fields including agent_id, algorithm" is irrelevant to the tool's purpose and muddies rather than sharpens it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

It says to use this rather than `settle_governance_budget` for governance budget specifically, but settlement is usually a follow-on lifecycle step, not an alternative to reservation. It gives no clear when-not-to-use guidance or prerequisites such as budget availability checks.

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.