Skip to main content
Glama

Synthex Forge — x402 Paid Agent Services

by com.synthexforge.x402
OverviewDiscussionsAdmin

Release Treasury Reservation

release_treasury_reservation
Destructive

Release a reservation, or reconcile an ambiguous transaction. use it rather than authorize_treasury_spend for treasury reservation, not treasury spend; an object with 3 fields including exception, field. $0.25 USDC.

Input Schema

NameRequiredDescriptionDefault
actionNoThe action being recorded or evaluated.release
reasonNoWhy the action is being taken. Recorded verbatim in the signed artifact.
txn_idNoThe txn id this operation operates on. See the schema for its type and whether it is required.
requestIdNoA caller-supplied idempotency key. The same key returns the same result instead of charging twice.
payment_refNoThe payment reference the operation concerns.

Output Schema

NameRequiredDescriptionDefault
fieldNoThe `field` field of the response.
exceptionNoThe `exception` field of the response.
request_idNoThe `request_id` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • 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 / request_id
      Added value: +{
+  "description": "The `request_id` field of the response.",
+  "type": "object"
+}
    • removedOutput schema / properties / status
      Removed value: -{
-  "type": "string"
-}
  2. Added

TDQS

B3.2/5.0
Behavior3/5

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

Adds genuinely useful non-structural context: a stated price of $0.25 USDC per call. Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered, but the description never says what releasing destroys, whether it can be undone, or what authorization is needed for a destructive financial mutation.

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 formed: an incomplete clause ("an object with 3 fields including exception, field") and a dangling price tag are appended after the useful guidance. Front-loading is present in the first clause but the remainder is noise rather than earned content.

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 destructive, non-idempotent financial mutation with five optional parameters and no required field, the description should say what state is released and what the caller must supply. It instead gives cost and a broken output fragment; the existence of an output schema excuses return-value detail but not the missing mutation semantics.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter (action, reason, txn_id, requestId, payment_ref) is already documented in the schema; baseline is 3. The description adds only the fragment about an object "with 3 fields including exception", which appears to describe a response shape rather than clarifying parameters, so no meaningful lift over the schema.

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?

States a concrete verb+resource ("Release a reservation") plus a second mode ("reconcile an ambiguous transaction"), and explicitly names the sibling it is not (authorize_treasury_spend). The trailing fragment ("an object with 3 fields including exception, field") is leftover text that slightly muddies an otherwise identifiable 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?

Provides one explicit routing rule: use this rather than `authorize_treasury_spend` for a reservation, not a spend. However, the second advertised mode (reconciling ambiguous transactions) has no stated trigger condition, and the phrasing of the alternative-selection sentence is garbled enough to require interpretation.

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 toolsInspect
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.

Resources