Skip to main content
Glama

quote_order

Validate an order and return the $5 call-placement fee, a Stripe checkout URL for the human, and x402 payment terms. Requires termsAccepted true and termsVersion 2026-11-17 (the human must have agreed). Does not charge and does not call the restaurant.

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": "quote_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
consentYes
allergiesNo
orderTypeYes
placeTokenYes
customerNameNo
termsVersionYes
customerPhoneNo
termsAcceptedYes
deliveryAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that nothing is charged, the restaurant is not contacted, a specific terms version must have been accepted by a human, and that a Stripe URL is produced for handoff. It does not cover failure modes, idempotency, or what a failed validation returns, which are meaningful gaps for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose and returns first, hard preconditions second, negative scope last. No filler and nothing buried.

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

Completeness3/5

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

Return values are described well enough to substitute for the absent output schema, but a 10-parameter, 6-required tool with no annotations and no parameter descriptions leaves too much of the input contract unexplained for the definition to be considered complete.

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 description coverage is 0% across 10 parameters, so the description must compensate. It only clarifies termsAccepted, termsVersion, and (indirectly) consent; placeToken, items, orderType, allergies, customerName, customerPhone, and deliveryAddress remain entirely undocumented, and termsVersion's valid value format is given but the rest of the contract is not.

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 ('Validate an order') plus exactly what is returned (a $5 fee, a Stripe checkout URL, x402 payment terms), and explicitly bounds the operation ('Does not charge and does not call the restaurant'), which separates it cleanly from place_order.

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?

Preconditions are stated ('Requires termsAccepted true and termsVersion 2026-11-17') and the negative scope tells an agent this is the pre-payment step rather than the order-placement step. It stops short of explicitly saying 'call this before place_order', so the ordering is inferred rather than stated.

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