Skip to main content
Glama

Servd Agentic Ordering

Place confirmed restaurant order

place_order
DestructiveIdempotent

Create a REAL restaurant order only after showing the latest validate_cart result and receiving explicit diner confirmation. A venue explicitly marked agentOrdering.sandbox instead returns a no-charge, no-kitchen simulation with sandbox=true and createsProductionOrder=false. Pass that result’s confirmation.token so the server can prove the cart and live quote did not change. The server recalculates all prices. Use a unique idempotency key, show orderNumber and the labeled customerLinks, and poll check_order for payment and fulfillment status. Unpaid online orders expire after 30 minutes.

Input Schema

NameRequiredDescriptionDefault
slugYesThe venue slug returned by find_venues.
itemsNo
combosNo
customerYesThe diner’s minimum contact details required by the venue.
deliveryNoFor delivery, street is required and coordinates may be needed for fees/radius.
branch_idNoBranch used for menu discovery and quote; retain it through confirmation and order placement.
confirmedYesSet true only after the diner explicitly confirms the latest validate_cart result.
tip_amountNoMajor currency units.
fulfillmentYes
payment_methodNoonline
idempotency_keyYesUse validate_cart.confirmation.idempotencyKey exactly; reuse it for retries of this confirmed order.
confirmation_tokenYesThe short-lived confirmation.token from the exact validate_cart result shown to the diner.

Output Schema

NameRequiredDescriptionDefault
messageYes
orderIdYesMachine-facing private id for check_order.
sandboxYes
trackUrlYes
expiresAtYes
statusUrlYes
friendlyIdYes
paymentUrlYes
checkoutUrlYes
orderNumberYesCustomer-facing order number.
paymentModeYes
trackingUrlYes
paymentErrorYes
customerLinksYes
paymentProviderYes
paymentRequiredYes
createsProductionOrderYesFalse for reviewer sandbox receipts. True only when a production order was created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / combos / items / properties / component_modifiers / items / properties / slot_index
      Added value: +{
      +  "description": "Zero-based combo item slot; required when an item occurs in multiple slots",
      +  "maximum": 49,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / branch_id
      Added value: +{
      +  "description": "Branch used for menu discovery and quote; retain it through confirmation and order placement.",
      +  "format": "uuid",
      +  "type": "string"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / combos / items / properties / component_modifiers
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "menu_item_id": {
      +        "maxLength": 128,
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "selected_modifiers": {
      +        "items": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "group": {
      +              "maxLength": 200,
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "name": {
      +              "maxLength": 200,
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "price_adj": {
      +              "description": "Informational major-unit amount from get_menu; the server recalculates it.",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "group",
      +            "name"
      +          ],
      +          "type": "object"
      +        },
      +        "maxItems": 50,
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "menu_item_id",
      +      "selected_modifiers"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 100,
      +  "type": "array"
      +}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive/openWorld/idempotent, but the description adds what they cannot: the server recalculates all prices, the confirmation token proves cart and live quote are unchanged, sandbox venues return sandbox=true and createsProductionOrder=false with no charge, and unpaid online orders expire after 30 minutes. These are exactly the behavioral traits an agent needs before committing a real order.

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?

Front-loaded with the hard precondition and no filler sentences; each sentence carries operational content. It is dense but appropriate for a 12-parameter destructive tool, though the idempotency wording is slightly redundant with the schema and risks misreading.

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?

For a high-risk 12-parameter mutation with nested items/combos, the description covers prerequisites, token provenance, pricing authority, sandbox semantics, post-call verification, and expiry handling. Since an output schema exists, it correctly stops short of enumerating return fields while still pointing at orderNumber and customerLinks.

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 67% and already documents confirmation_token, idempotency_key, confirmed, branch_id, delivery and tip. The description reinforces the two critical ones by tying confirmation_token to 'the exact validate_cart result shown to the diner' and explaining why a distinct idempotency key matters, but it does not disambiguate items vs combos or the items/combos anyOf constraint. One minor tension: description says 'unique idempotency key' while the schema says reuse validate_cart.confirmation.idempotencyKey exactly.

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?

States a specific verb and resource ('Create a REAL restaurant order') plus the precondition that distinguishes it from validate_cart and check_order. The sandbox branch is named explicitly, so an agent knows this single tool covers both a production order and a simulated one.

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

Usage Guidelines5/5

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

Gives explicit when-to-use conditions (only after showing the latest validate_cart result and receiving explicit diner confirmation), names the downstream sibling (poll check_order), and discloses the sandbox exclusion path. Nothing about sequencing is left to inference.

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