Skip to main content
Glama

Start a crypto payment

start_crypto_payment

For an order token from create_order: files the payment details (rail usdc_base, billing address with a two-letter state for the US, the wallet the buyer pays from, role, acceptance) and Beacon emails a one-time code to the buyer's own inbox (the order's email address), never to the agent. Answers the order's status.

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>",
      "rail": "<rail>",
      "billing": "<billing>",
      "role": "<role>",
      "wallet_address": "<wallet_address>",
      "accept": "<accept>"
    },
    "name": "start_crypto_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYes
roleYes
phoneNothe buyer's phone, if not given at create_order
acceptYestrue only when the buyer has read and accepted the Terms of Service including Schedule C, the refund policy and the Privacy Policy (https://aruon.ai/terms-of-service, https://aruon.ai/privacy)
billingYes
order_tokenYes
wallet_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare non-readonly/non-destructive/non-idempotent, so the description adds real value: it discloses that Beacon emails a one-time code to the buyer's own inbox and never to the agent, and that the call returns the order's status. It omits retry/no-idempotency implications of a non-idempotent call, which would have pushed it higher.

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?

One dense sentence that front-loads the prerequisite before the mechanics and the OTP caveat. Nothing is wasted, though the parenthetical nesting makes it slightly harder to scan.

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?

For a 7-parameter nested-object tool with no output schema, the description covers the prerequisite, the key behavioral side effect, and the shape of the result. Minor gaps remain around the phone parameter and what the returned status values mean.

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 29%, so the description must compensate, and it does for most fields: it names the rail value usdc_base, explains that the billing address needs a two-letter state for US addresses, describes the wallet as the one the buyer pays from, and characterizes role and acceptance. It leaves phone and the order_token format 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?

Uses a specific verb and resource ('files the payment details' for a crypto rail, triggers an OTP email) which is clearly distinct from create_order and get_order_status. It does not explicitly differentiate from confirm_crypto_payment, so it stops short of 5.

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?

States the prerequisite clearly ('For an order token from create_order'), which tells the agent when this tool is applicable. It never says when not to use it or how it relates to confirm_crypto_payment, so the guidance is implied rather than explicit.

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