Skip to main content
Glama

Confirm a crypto payment

confirm_crypto_payment
Idempotent

For the code the buyer received: answers the quote, or the hold and who must act. The quote is an exact amount (price, 5% Texas sales tax and a small unique tail), a receive address and a 20-minute window to send it, from the wallet declared. The agent never pays: the buyer sends from their own wallet. Paying publishes nothing by itself: a person at Aruon reviews the build, and the site owner approves a preview before anything goes live.

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_token": "<order_token>",
      "code": "<code>"
    },
    "name": "confirm_crypto_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYes
order_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false, idempotentHint=true and openWorldHint=false; the description adds genuinely useful process context (20-minute send window, exact amount including tax and a unique tail, buyer pays from their own wallet, human review and owner preview approval before publishing). What it never discloses is the tool's own effect: readOnlyHint=false implies a state change, yet the description only speaks about the payment flow, leaving it unclear what this call itself writes.

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 opening fragment is tangled and front-loads process narrative ahead of the tool's actual function. Two of the four sentences describe downstream payment/human-review mechanics that are tangential to invoking this tool correctly, and key details like the receive-address/quote return shape are buried mid-sentence.

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?

With no output schema, the description must explain what comes back, and "answers the quote, or the hold and who must act" is too vague to tell an agent what fields or states to expect. Combined with the undocumented `order_token` and the unexplained write behavior (readOnlyHint=false), an agent lacks enough to call this confidently.

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 0%, so the description must carry the parameter meanings. It loosely explains `code` ("the code the buyer received") but `order_token` is never mentioned at all, leaving half the required surface undocumented in both schema and prose.

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 name says "confirm" but the description opens with "answers the quote, or the hold and who must act," which reads like a retrieval of quote/hold state rather than a confirmation action. The agent can infer this resolves a buyer-supplied code into a quote or hold, but the core verb is never stated plainly, and it is not distinguished from siblings such as start_crypto_payment or request_new_quote.

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?

"For the code the buyer received" supplies an implied trigger condition for use, which is better than nothing. However, no alternatives are named and no when-not condition is given, so the agent must guess whether this or get_order_status / start_crypto_payment is the right call in a given situation.

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