Skip to main content
Glama

order_purchase

Destructive

Request a purchase of a quote. Charges nothing: returns an approval link for the user to review and pay on Stripe's page. The card is held, and charged only once the printer accepts.

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": "<order>",
      "quote": "<quote>"
    },
    "name": "order_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesOrder id (ord_…).
quoteYesThe quote to buy (qte_…), usually recommended_quote_id.
max_totalNoRefuse if the total is above this, in the order's currency (USD, e.g. 450).

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

This is the tool's strongest aspect. Although the annotations mark it destructiveHint=true and idempotentHint=false, the description explains the actual money flow: the call returns an approval link, the card is only held, and the charge happens only after the printer accepts. That context matters because an agent could otherwise avoid a 'destructive' tool on false grounds.

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?

It uses three short sentences, and the key reassurance ('Charges nothing') is placed immediately after the purpose. No sentence is wasted, although the last two sentences overlap somewhat on the money behavior.

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?

An output schema exists, so the return value does not need a full explanation, and the approval-link mention is a useful bonus. The remaining gap is the retry and idempotency story: because the tool is non-idempotent, it should tell the agent what happens if the approval link is called twice.

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 the schema already documents all three parameters, including what max_total does. The description adds context about the charge behavior, but it does not explain what max_total means against a held versus a final amount, so the schema has to carry that burden.

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 names a specific verb and resource: requesting a purchase of a quote. That is clear enough for an agent to distinguish it from order_quote or order_create. It does not name any sibling tool, so differentiation relies on inference.

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?

It implies that this is the step that turns a quote into a purchase, and it says the user pays on Stripe's page. It never states when to prefer it over order_quote, order_create, or order_cancel, and it gives no preconditions, such as needing a quote that is still valid.

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