Skip to main content
Glama

Create order and get payment link

create_order

USE THIS when the human says yes to a specific item. Creates the order and returns pay_url plus a ready-to-say sentence. It never charges a card: the human opens pay_url and approves payment themselves. Say the returned line to the human verbatim. Stock hold: the item is reserved for 24 hours after create_order; if payment is not approved within 24 hours the order auto-cancels and the hold is released. Payment facts: PayPal Business account, PayPal balance / debit card / credit card (Visa, Mastercard, Amex, Discover); a PayPal account is NOT required; USD; the total already includes US duty, shipping and clearance. Never ask for card numbers, CVV or expiry, and never pay on the human's behalf. Full facts: GET /api/payment.json.

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": {
      "product_id": "<product_id>"
    },
    "name": "create_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNo
testNotrue = dry run, no stock taken, no email sent
buyerNo
product_idYes
idempotency_keyNosame key returns the same open order

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only cover readOnlyHint=false and destructiveHint=false, so the description has to explain the real side effects, and it does: a 24-hour stock hold, auto-cancel on non-payment, and no card charge. The payment facts (accepted methods, currency, duties included, no PayPal account needed) and a pointer to /api/payment.json add context an agent cannot get from the annotations.

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 is front-loaded with "USE THIS" and organized into labeled blocks (stock hold, payment facts, prohibitions), which is easy to scan. The payment-method enumeration is a bit long, but it replaces questions the agent would otherwise ask the human.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description says what comes back (pay_url plus a verbatim line to say) and what happens after creation (24-hour hold, auto-cancel). Combined with the safety prohibitions, an agent can call this correctly without extra context.

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 coverage is only 40%, and the description explains no parameters at all: qty, the nested buyer object (name, email, address, zip, country), and test/idempotency_key are left to the schema. It spends its length on payment facts and return values instead of closing the parameter documentation gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Creates the order") and names the return contract ("returns pay_url plus a ready-to-say sentence"), which an agent can use to tell it apart from quote/preview tools. The trigger phrase "when the human says yes to a specific item" pins down the exact moment this tool applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit positive trigger (human says yes) and strong exclusions: don't charge cards, don't ask for card numbers, don't pay on the human's behalf. It never names an explicit alternative for the pre-yes or quote case, so the agent must infer the boundary with quoting tools.

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