Skip to main content
Glama

Settle an x402 payment for somebody else's wallet (paid, x402)

settle_payment

PAID: send the {paymentPayload, paymentRequirements} pair our free POST /verify takes and we broadcast the USDC transfer your payer signed to YOUR payTo out of our gas float, for $0.0200 a call whatever the amount settled. Scheme exact, USDC on Base, Base Sepolia and Solana. No facilitator or gas of your own. No transfer, no sale: the fee is held as one prepaid call. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "settle_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentPayloadNoThe signed x402 payload your payer produced, decoded, as it would ride in their X-PAYMENT header.
paymentRequirementsNoThe requirements it was signed against: scheme, network, maxAmountRequired, payTo, asset, each a string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, it discloses pricing ($0.0200 flat regardless of settled amount), the prepaid-call billing model, that gas comes from the provider's float, supported chains, and the unpaid response. That is substantial context the annotations do not carry. One tension is unaddressed: broadcasting an irrevocable on-chain USDC transfer is not described in terms of irreversibility or failure handling, and it sits oddly beside openWorldHint=false, though this is a debatable reading rather than a clear contradiction.

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

Conciseness4/5

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

The critical fact (PAID) is front-loaded and the sentences are dense with decision-relevant information. It is somewhat run-on, with two overlapping chain lists and a trailing feedback/"read daily" line that does not help an agent decide or invoke, which keeps it from a 5.

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

Completeness3/5

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

For a paid, state-changing settlement tool with no output schema, the description covers cost, networks, and the unpaid path but says nothing about what a successful call returns (transaction hash, settlement receipt, confirmation status) or what happens if the broadcast fails. That is the main gap an agent would hit after calling.

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 coverage is 100%, so the baseline is 3, but the description adds real provenance: the payload is the decoded signed x402 object as it would ride in the payer's X-PAYMENT header, and the requirements are what it was signed against. That tells an agent where the values come from, which the schema does not.

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" plus the specific resource (a signed x402 {paymentPayload, paymentRequirements} pair) and the scope "for somebody else's wallet / to YOUR payTo" is a concrete verb+resource statement that an agent can act on. It implicitly separates itself from a plain self-payment by stressing third-party settlement and the gas float, but it never names or contrasts a sibling tool, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

It states the precondition clearly: you must already hold the payload pair that POST /verify accepts, and the payer must have signed a USDC transfer to your payTo. It also gives the retry path when unpaid (returns the price, pay via _meta['x402/payment'], call again). It stops short of explicit exclusions versus alternatives such as pay_send or relay_usdc.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources