Synthex Forge — x402 Paid Agent Services

Settle Governance Budget

settle_governance_budget

Destructive

Agent Spend Governor — settle a lease, idempotent. use it rather than reserve_governance_budget for governance budget specifically; an object with 9 fields including algorithm, detail. $0.02 USDC.

Input Schema

Name	Required	Description	Default
`lease_id`	Yes	The lease id this operation operates on. See the schema for its type and whether it is required.
`actual_amount`	Yes	The actual amount this operation operates on. See the schema for its type and whether it is required.

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.
`lease_id`	No	The `lease_id` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`public_key`	No	The `public_key` field of the response.
`settled_at`	No	The `settled_at` field of the response.
`signed_over`	No	The `signed_over` 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 / 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 / lease_id

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

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

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

C2.8/5.0

Behavior1/5

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

The description asserts the operation is "idempotent", while the annotations declare `idempotentHint: false` — a direct contradiction on a behaviorally significant trait. The genuinely useful detail ("$0.02 USDC" cost) does not offset declaring the opposite of the structured hint.

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

Conciseness3/5

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

It is short and front-loads the tool identity and price, but the clause "an object with 9 fields including algorithm, detail" is vague boilerplate that conveys little and competes with the far more important lease/cost information.

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 `destructiveHint: true` on a budget-spending mutation, the agent needs to know what gets debited and whether the lease is consumed; the description says nothing about that. The output schema exists, yet the description still gestures at return fields vaguely instead of covering the destructive semantics.

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 `lease_id` and `actual_amount` are already documented structurally. The description adds no format, range, or semantics (e.g. whether actual_amount may exceed the reserved lease) beyond the schema baseline.

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?

"Settle a lease" gives a specific verb and resource, and the description explicitly routes the agent away from `reserve_governance_budget`. It is distinguishable from the sibling reserve tool, though "settle" in the governance-budget sense is not fully defined.

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

Usage Guidelines3/5

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

It names an alternative (`reserve_governance_budget`) but frames it as a substitute rather than the natural counterpart — the agent is told to use settle "rather than" reserve, which is arguably backwards for a reserve/settle lifecycle. No precondition (e.g. an existing lease_id) or exclusion is stated.

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.