Skip to main content
Glama

place_order

Does not place the call by itself. Returns how to pay the $5 fee (Stripe checkout URL for the human, or x402 USDC on Base) and the endpoints to call after payment. Paid placement is a separate HTTP POST after payment is confirmed.

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": {
      "placeToken": "<placeToken>",
      "items": "<items>",
      "orderType": "<orderType>",
      "termsAccepted": "<termsAccepted>",
      "termsVersion": "<termsVersion>",
      "consent": "<consent>"
    },
    "name": "place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
payRefNo
consentYes
allergiesNo
orderTypeYes
placeTokenYes
customerNameNo
termsVersionYes
customerPhoneNo
termsAcceptedYes
deliveryAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: a $5 fee, two payment rails (Stripe checkout for a human, x402 USDC on Base), and that placement is a distinct post-payment call. It omits failure modes, whether the fee is charged on retry, idempotency of placeToken, and what happens if terms or consent are not supplied, which matters for an 11-parameter mutation.

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?

Three short sentences with the most important caveat front-loaded: an agent reading only the first clause already knows this is not the final placement step. The phrasing "the call" and "paid placement" is the only wasteful ambiguity.

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?

For a tool with 11 undocumented parameters, no annotations, and no output schema, the description should explain inputs and return shape. It gestures at the return value (checkout URL, endpoints) but leaves the entire input contract and the post-payment handoff details unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 11 parameters, six of them required, so the description must compensate and it explains none of them. Critical fields such as placeToken, termsAccepted, termsVersion, consent, and the pickup/delivery enum are left entirely undefined in both places.

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 description clearly states what the tool does NOT do (it does not complete the placement) and what it returns: a payment path and follow-up endpoints. However, it never mentions orders, food, or pickup/delivery, and instead talks about "the call" and "paid placement," which does not line up with the name place_order or the items/orderType/deliveryAddress schema. An agent learns the payment framing but not what business action it is initiating.

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

Usage Guidelines2/5

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

There is useful sequencing guidance: payment must be confirmed before a separate HTTP POST completes the placement. But there is no guidance on when to call this versus quote_order or order_status, and no mention of prerequisites such as needing a placeToken or accepted terms first. The agent must infer the workflow position from the schema alone.

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