Skip to main content
Glama

Servd Agentic Ordering

Validate and price cart

validate_cart
Read-onlyIdempotent

Validate a proposed cart and calculate authoritative lines, discounts, fees, tax and total without creating an order. Call this immediately before asking the diner to confirm. Send only the minimum diner contact and fulfillment data required for this order.

Input Schema

NameRequiredDescriptionDefault
slugYesThe venue slug returned by find_venues.
itemsNo
combosNo
customerNo
deliveryNo
branch_idNoBranch used for menu discovery and quote; retain it through confirmation and order placement.
tip_amountNoMajor currency units.
fulfillmentYes
payment_methodNoonline

Output Schema

NameRequiredDescriptionDefault
linesYes
validYes
venueYes
totalsYes
fulfillmentYes
paymentModeYes
confirmationYes
createsOrderYes
requirementsYes
paymentMethodYes

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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the pricing returned is 'authoritative' (server computes it, not the agent) and no order is created — plus a data-minimization directive. It stops short of saying whether the quote expires or must be re-validated later.

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 sentences, no filler, with the core verb-and-scope statement front-loaded. The final sentence on minimal data is a behavioral directive rather than description, but it earns its place by shaping how the agent fills customer/delivery.

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 a 9-param, deeply nested tool with an output schema and strong annotations, the description covers purpose, sequencing and input minimization. The remaining gap — no mention that items and combos are mutually exclusive alternatives — is the one thing an agent could plausibly get wrong from this text alone.

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 only 33% across 9 params, so the description carries more burden than usual. Its 'send only the minimum diner contact and fulfillment data' line usefully scopes the customer/delivery objects, but it says nothing about the items-vs-combos anyOf, which is the single easiest way to get this call wrong.

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 uses a specific verb pair (validate, calculate) on a specific resource (a proposed cart) and enumerates the outputs (lines, discounts, fees, tax, total). Crucially it states 'without creating an order', which distinguishes it from the place_order sibling without the agent needing to open either schema.

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?

'Call this immediately before asking the diner to confirm' gives an explicit timing trigger that sequences the tool against place_order. What's missing is naming the alternative outright ('use place_order to actually submit') or stating when-not-to-call conditions, so it falls short of a full when/when-not/alternatives statement.

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