Skip to main content
Glama

Pay an order

pay_order
Destructive

Submit payment: tx_hash (EVM hash or Solana signature) of your transfer, or x_payment (base64 x402 EIP-3009 payload, gasless).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "order_id": "<order_id>"
    },
    "name": "pay_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoOptional. Guest or dashboard API key (sd_live_…). Prefer Authorization: Bearer <key> on the MCP connection; if your client cannot set headers, pass the key here.
tx_hashNo
order_idYes
x_paymentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "Optional. Guest or dashboard API key (sd_live_…). Prefer Authorization: Bearer <key> on the MCP connection; if your client cannot set headers, pass the key here.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/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=true, so the safety profile is covered. The description adds real value by disclosing the two payment modes and their formats (on-chain hash vs. gasless EIP-3009 payload), but says nothing about what happens after submission, whether an already-used hash is rejected, or that a retry is unsafe given non-idempotency.

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?

A single dense sentence, front-loaded with the action and immediately followed by the two payment options. Every clause carries information; only minor friction comes from the compressed parenthetical stacking.

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 destructive, non-idempotent payment tool with no output schema and thin schema coverage, the definition covers the mechanics of providing proof-of-payment but omits amount matching, order state requirements, and failure/retry semantics. An agent could call it, but not confidently reason about edge cases.

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 only 25% (only api_key is documented), so the description must compensate and largely does: it specifies that tx_hash is an EVM hash or Solana signature and that x_payment is a base64 x402 EIP-3009 payload. The 'or' framing usefully implies the two payment parameters are mutually exclusive, though order_id itself is left unexplained.

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 description opens with a specific verb, 'Submit payment', and the resource is evident from the name/title (an order). It implicitly distinguishes itself from balance-based siblings by requiring an external transfer hash or x402 payload, though it never names an alternative tool.

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?

Usage is only implied: 'of your transfer' signals that funds must already have been sent before calling, and the 'or x_payment ... gasless' clause presents two payment paths. There is no explicit statement of when to choose this over buy_with_balance, no prerequisite that an order must exist first, and no when-not guidance.

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