Skip to main content
Glama

Ask for a product for a website, paid in crypto

create_order

Records an order request for a website's owner (the principal). Nothing is charged. While crypto is open for the contact_email, rail usdc_base answers an order_token, and no operator key is needed: start_crypto_payment is next. Otherwise, with a crypto rail, an approved operator gets a crypto quote (exact amount, address, 20-minute send window) next to the card link, or a hold that waits for a person or for the principal; every other request is answered pending_review and a person at Aruon reviews it. Without rail, or with rail "card", it is a card order. A person at Aruon checks the first order from a new agent operator or a new buyer before anything goes live; the payment service can also hold an order before it is quoted. Once quoted, a payment on Base can take about 20 minutes to finalise after the send. A person reviews first-time and large orders. 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": {
      "sku": "<sku>",
      "site": "<site>",
      "contact_email": "<contact_email>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesa sku from list_products with a crypto total
railNocard (the default, as with no rail): the website's card path, where an approved operator gets the product's checkout link for the site owner; this service itself answers a card order pending_review and a person at Aruon reviews it. Or one of list_products' railscard
siteYesthe website, e.g. example.com
contactNohow a person at Aruon reaches the operator; required with a crypto rail
principalNothe site owner's details for the payment service's intake (all optional here; what is still missing comes back in principal.missing)
operator_idNoyour operator id, given by Aruon with your key
operator_keyNoyour operator key, given by Aruon
ai_agent_nameNorequired with a crypto rail
contact_emailYesthe site owner's email address
agent_operatorNorequired with a crypto rail
authorization_statementNothe principal's authorisation of this agent, logged; required with a crypto rail

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / agent_operator
      Added value: +{
      +  "description": "required with a crypto rail",
      +  "type": "string"
      +}
    • addedInput schema / properties / ai_agent_name
      Added value: +{
      +  "description": "required with a crypto rail",
      +  "type": "string"
      +}
    • addedInput schema / properties / authorization_statement
      Added value: +{
      +  "description": "the principal's authorisation of this agent, logged; required with a crypto rail",
      +  "type": "string"
      +}
    • addedInput schema / properties / contact
      Added value: +{
      +  "description": "how a person at Aruon reaches the operator; required with a crypto rail",
      +  "type": "string"
      +}
    • addedInput schema / properties / principal
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "the site owner's details for the payment service's intake (all optional here; what is still missing comes back in principal.missing)",
      +  "properties": {
      +    "billing": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "city": {
      +          "type": "string"
      +        },
      +        "country": {
      +          "type": "string"
      +        },
      +        "line1": {
      +          "type": "string"
      +        },
      +        "line2": {
      +          "type": "string"
      +        },
      +        "postal": {
      +          "type": "string"
      +        },
      +        "region": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "declared_wallets": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "address": {
      +            "type": "string"
      +          },
      +          "family": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "family",
      +          "address"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "intended_use": {
      +      "type": "string"
      +    },
      +    "legal_name": {
      +      "type": "string"
      +    },
      +    "organization": {
      +      "type": "string"
      +    },
      +    "phone": {
      +      "type": "string"
      +    },
      +    "role": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / rail
      Added value: +{
      +  "default": "card",
      +  "description": "card (the default, as with no rail): the website's card path, where an approved operator gets the product's checkout link for the site owner; this service itself answers a card order pending_review and a person at Aruon reviews it. Or one of list_products' rails",
      +  "enum": [
      +    "card",
      +    "btc",
      +    "eth_ethereum",
      +    "usdc_ethereum",
      +    "usdc_base"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / sku / description
      Previous value: -"a sku from list_products"New value: +"a sku from list_products with a crypto total"
  2. First observed

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does substantial work: it discloses that nothing is charged, that orders can land in pending_review, that first-time/new-operator orders get human review, that an approved operator receives an exact amount, address and a 20-minute send window, and that payment publishes nothing without owner preview approval. What it omits is idempotency behavior, error/retry semantics, and what identity is required in which branch beyond the terse 'no operator key is needed' clause.

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 first two sentences are well front-loaded, but the remainder is a dense run-on chain of conditional clauses ('While crypto is open for the contact_email, rail usdc_base answers an order_token...') that is hard to parse on first read. Human-review behavior is restated three separate times ('a person at Aruon reviews', 'A person at Aruon checks', 'A person reviews first-time and large orders'), wasting space in an already bloated paragraph.

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 an 11-parameter tool with a nested principal object and no output schema, the description does cover the outcome states an agent needs (order_token, pending_review, quote with send window, hold), including response-ish terms like principal.missing that appear nowhere else. Gaps remain around authorization failure modes and whether repeated calls create duplicate orders, but the core workflow is legible.

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 description coverage is 100%, so the schema already explains sku, rail, contact, principal.missing, and the several 'required with a crypto rail' fields; the description adds little on top. The only marginal additions are the implicit 'nothing is charged' framing and the pending_review outcome for the default card rail, which the rail enum description already states.

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 opening sentence states a specific verb and resource: 'Records an order request for a website's owner (the principal). Nothing is charged.' That is unambiguous. However, it never positions itself against the actual siblings (get_order_status, list_products); it instead names start_crypto_payment, which is not in the sibling list, so the agent gets no routing contrast for follow-up calls.

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?

There is implied conditional guidance: with crypto open for the contact_email, 'start_crypto_payment is next'; with a card rail, the checkout link path applies; otherwise pending_review. That tells the agent what happens downstream but nowhere states the positive trigger for choosing create_order over checking an existing order. No when-not guidance and no reference to get_order_status as the alternative for existing orders.

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