Skip to main content
Glama

Reserve a table

restaurant_reservation
Read-only

Open the optional reservation form widget (OpenAI restaurant-reservation entry point). ONLY call this when the user taps a Reserve button on a venue card or asks for a booking form. conversational booking is the default: if they just ask to book in chat, collect the details and call request_reservation directly, and never re-collect details they already gave. Pass the place id as restaurant_id.

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": {
      "restaurant_id": "<restaurant_id>"
    },
    "name": "restaurant_reservation"
  }
}

Input Schema

NameRequiredDescriptionDefault
restaurant_idYesPlace id from a search result.
restaurant_nameNoOptional display name for optimistic rendering in the modal.
restaurant_imageNoOptional image URL for optimistic rendering.
restaurant_addressNoOptional structured address for optimistic rendering.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description usefully adds that this surfaces a UI widget rather than completing a booking, which is the key behavioral distinction. It does not say what the widget returns or how the flow continues after it closes, which keeps it below a 5.

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, front-loaded with the action, then the gating condition, then the fallback path. There is no redundant restatement of the title or schema fields.

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 widget-launcher with four documented parameters, one required, the description covers the routing decision that matters most. It leaves open what the widget hands back to the agent, which is the only real gap given there is no output schema.

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 100% and every parameter, including the nested address object, already carries a description, so the baseline is 3. The description adds only the pointer that the place id goes in restaurant_id, which the schema field description already conveys.

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 states a specific action on a specific resource: it opens the optional reservation form widget and passes the place id as restaurant_id. It also explicitly separates itself from request_reservation, so an agent can pick between the two without inspecting 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 Guidelines5/5

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

It gives an explicit ONLY condition (user taps a Reserve button on a venue card or asks for a booking form), states the default alternative (conversational booking via request_reservation), and adds a behavioral rule not to re-collect details the user already gave. When-to-use, when-not-to-use, and the alternative are all named.

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.