Synthex Forge — x402 Paid Agent Services

Get Treasury Budget

get_treasury_budget

Read-onlyIdempotent

Set the budget limit for an agent or customer scope. use it rather than authorize_treasury_spend for treasury budget, not treasury spend; 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.
`limit_usd`	No	The limit usd 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.

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

C2.3/5.0

Behavior1/5

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

The description says 'Set the budget limit', which is a write/mutation operation, while annotations declare readOnlyHint=true. This is a serious contradiction: an agent could infer a read operation from annotations or a write operation from the description. The mention of '$0.25 USDC' adds pricing context, but the core behavioral signal is contradictory.

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 poorly structured: it begins with a clear clause, then degenerates into a semicolon-separated fragment with an inaccurate field count and an isolated price note. Conciseness here comes at the cost of coherence rather than being front-loaded and efficient.

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?

There is an output schema, so return values need not be described. But the description contradicts the readOnly annotation and misstates the input schema fields. For a budget-limit operation, it should clarify whether this sets or gets budget state and how idempotency/pricing apply; instead it leaves key behavioral questions unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 documents the actual parameters: scope, limit_usd, and requestId. The description instead claims 'an object with 5 fields including exception, field', which does not match the 3-field schema and introduces non-existent parameter names, adding misleading rather than useful semantic detail.

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 action and resource: 'Set the budget limit for an agent or customer scope.' However, this directly conflicts with the tool name and title, both of which say 'Get', making the actual purpose unreliable. The fragmentary mention of 'an object with 5 fields including exception, field' adds confusion rather than clarity.

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 a sibling alternative explicitly: use this rather than `authorize_treasury_spend` for treasury budget, not treasury spend. That is useful routing information, but the phrasing is garbled and does not clearly explain when-not-to-use this tool beyond the one sibling comparison.

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.