Synthex Forge — x402 Paid Agent Services

Authorize Treasury Spend

authorize_treasury_spend

Destructive

Evaluate the policy, then ATOMICALLY reserve the budget. use it rather than commit_treasury_spend for treasury spend specifically; an object with 5 fields including exception, field. $0.25 USDC.

Input Schema

Name	Required	Description
`scope`	No	The scope this operation operates on. See the schema for its type and whether it is required.
`intent`	No	The commercial intent the operation evaluates.
`policy`	No	The policy document or policy id the decision is evaluated against.
`agent_id`	No	The identifier of the agent the operation concerns.
`principal`	No	The principal this operation operates on. See the schema for its type and whether it is required.
`requestId`	No	A caller-supplied idempotency key. The same key returns the same result instead of charging twice.
`amount_usd`	No	The amount in USD. The settlement rail converts it to the exact atomic amount.
`ttl_seconds`	No	How long the record stays valid, in seconds.
`policy_version`	No	Version of the policy the decision is bound to.
`idempotency_key`	No	The idempotency key this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`id`	No	The `id` field of the response.
`kind`	No	The `kind` field of the response.
`field`	No	The `field` field of the response.
`exception`	No	The `exception` field of the response.
`request_id`	No	The `request_id` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 31, 2026

addedOutput schema / properties / exception

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

addedOutput schema / properties / field

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

addedOutput schema / properties / id

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / request_id

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

removedOutput schema / properties / status

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

AddedOct 31, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful facts beyond them: the reservation is ATOMIC and the call costs $0.25 USDC. However it never explains what a reservation does to the budget, that it must later be released or committed, or why the operation is destructive.

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?

It is short but structurally broken: the semicolon splices a cost note onto an unrelated schema fragment ('an object with 5 fields including exception, field'), and the lowercase 'use it rather than' begins mid-thought. The atomicity and cost facts are valuable but are buried in a run-on rather than front-loaded.

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?

For a 10-parameter, destructive, non-idempotent money-moving tool, the description omits the reservation lifecycle (release via `release_treasury_reservation` vs. settle via `commit_treasury_spend`), the effect of `requestId`/`idempotency_key` given idempotentHint=false, and any note that all parameters are optional. An output schema exists, so return shape needn't be explained, but the lifecycle gap is material.

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% across all 10 parameters, so the schema already documents scope, policy, amount_usd, ttl_seconds, requestId and the rest. The description contributes nothing parameter-specific — the '5 fields including exception, field' fragment does not map to any of the ten inputs and only adds confusion. Baseline 3 applies when the schema carries the burden.

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?

The opening clause states a concrete two-step verb sequence (evaluate policy, then atomically reserve budget) on a named resource, and it explicitly distinguishes itself from the sibling `commit_treasury_spend`. The trailing fragment ('an object with 5 fields including exception, field') is unrelated noise that does not erase the clear core purpose.

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 one alternative and a selection condition: 'use it rather than `commit_treasury_spend` for treasury spend specifically.' That is real routing guidance, but there are no when-not conditions, no prerequisites (e.g. a policy must exist first), and no mention of the sibling `release_treasury_reservation` that undoes this operation.

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.