Skip to main content
Glama

book_table

Reserve a restaurant table and receive a confirmed reservation, cancel token, refund terms, and calendar invite; the refundable hold costs $0.01 in USDC per call.

Instructions

Book a restaurant table. Returns the confirmed reservation with a cancel token, refund terms and a calendar invite. The hold is refundable. Costs $0.01 per call, paid in USDC over x402 to x402-tablebook. Returns the merchant's artifact and the payment receipt.

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": {
      "date": "<date>",
      "time": "<time>",
      "party": "<party>",
      "name": "<name>"
    },
    "name": "book_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesYYYY-MM-DD
nameYesName on the reservation
railNoPayment rail for this call. Overrides the configured default (auto). auto = whichever rail this agent holds a key for.
timeYesHH:MM, 24-hour
notesNoRequests for the restaurant
partyYesParty size, 1-8

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A3.5/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 the cost ($0.01/call), the payment rail (USDC via x402 to x402-tablebook), that the hold is refundable, and what comes back (cancel token, refund terms, calendar invite, receipt). It omits failure behavior — e.g., whether the agent is still charged if the booking cannot be confirmed.

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?

The core action and outcome are front-loaded in three tight sentences. The payment fact is restated at the end ('Returns the merchant's artifact and the payment receipt') after already being covered by the pricing sentence, which is mild redundancy.

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?

No output schema exists, and the description compensates by enumerating the return payload (confirmed reservation, cancel token, refund terms, calendar invite, receipt). For a paid, real-world side-effecting booking tool the main remaining gap is what happens on failure or double-booking.

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 description coverage is 100%, so all six parameters including the rail enum are already documented in the schema. The description adds no parameter-level meaning such as how 'party' interacts with the price or how 'rail' affects billing, so baseline 3 is right.

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

Purpose4/5

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

States a specific verb and resource ('Book a restaurant table') that an agent can easily distinguish from the search-oriented siblings like find_tables or browse_catalog. It does not explicitly name or rule out any sibling, so it stops short of a 5.

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 no explicit when-to-use, when-not-to-use, or alternative routing (e.g., 'search with find_tables first'). The pricing note ('Costs $0.01 per call') implies the agent should call deliberately, but it is never framed as guidance or a prerequisite.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.