Skip to main content
Glama

agent-exec

Deliver an x402 authorization you signed, and check the chain (paid, x402)

pay_send

PAID: deliver an x402 payment you signed to a seller exactly once, verify it on chain, and get a receipt of what the seller answered. 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. Price: $0.0200 USDC.

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": "pay_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional request body for the seller.
dryRunNoOptional. true: a dry run -- nothing is sent or changed, and the 200 answer (served:true, dryRun:true) says what this call would do with the rest of your body, or which fields are missing. A dry run is a paid call at this price. false or absent: the call runs.
methodNoGET, POST, PUT, PATCH or DELETE.
headersNoOptional request headers for the seller, at most 20.
sellerUrlNoThe seller endpoint to deliver the authorization to, an absolute http:// or https:// URL.
authorizationNoThe authorization you already signed for the seller. This is NOT the payment that pays us -- that one goes in _meta.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds substantial behavior beyond annotations: exactly-once delivery, on-chain verification, receipt of the seller's answer, the 402-style price response when unpaid, accepted chains, price ($0.0200 USDC), and a no-reply feedback note. Minor tension: openWorldHint=false despite delivering to an arbitrary absolute http(s) seller URL, but the description doesn't explicitly assert closed-world behavior, so this reads as understated rather than contradictory.

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?

Front-loaded with the action and mode ('PAID:'), then the unpaid path and payment mechanics. Dense but every clause carries operational meaning; the trailing feedback/price sentence is slightly tacked-on but useful.

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

Completeness4/5

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

With no output schema and six parameters including a nested authorization object, the description supplies the missing protocol context: idempotency, verification, receipt contents, and the meta payment channel. It doesn't describe failure modes (e.g., verification failure, duplicate delivery) or the receipt's shape, which is the remaining gap.

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 coverage is 100%, so field meanings are already documented; the description's main added value is conceptual — clarifying that the `authorization` object is the payment to the seller while the payment to us goes in _meta, which is not visible from the schema. That is a helpful distinction but limited in scope.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('deliver an x402 payment you signed to a seller'), plus two side effects: verify on chain and return a receipt. It also disambiguates the unpaid path ('returns the price') vs the paid path, so an agent can distinguish this from a generic payment or check tool.

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?

Explains the two-step flow clearly: first call returns the price, then re-call with the payment in _meta['x402/payment']. It gives no explicit when-not guidance or named alternatives among siblings, but the paid/unpaid branching is enough context to pick the call correctly.

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.