Skip to main content
Glama
chrischall

opentable-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

opentable_search_restaurants

Read-only

Search OpenTable for restaurants by cuisine, location, date, and party size. Returns matching venues with cuisine, price band, rating, and URL, but no bookable time slots.

Instructions

Search OpenTable for restaurants. Returns matching restaurants with cuisine, neighborhood, price band, rating, description, and URL. Does NOT include bookable slot tokens — use opentable_find_slots for a specific venue to check availability.

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD. Affects search ranking but not returned slots.
termNoFree-text query (cuisine or restaurant name)
timeNoHH:MM (24h). Default 19:00 when date is set.
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns OpenTable's payload untouched. No field projection: this server has no verified record of which OpenTable fields matter, and inventing one would risk dropping a field a caller needs.
latitudeNo
locationNoCity / neighborhood / address — appended to the term. Prefer lat/lng when precise.
metro_idNoOpenTable metro id (e.g. 8 = SF Bay Area, 31 = Charlotte).
longitudeNo
party_sizeNoNumber of guests. Default 2.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changedv0.19.2
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns OpenTable's payload untouched. No field projection: this server has no verified record of which OpenTable fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  3. First observedv0.14.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds valuable behavioral context by enumerating the returned fields (cuisine, neighborhood, price band, rating, description, URL) and the key negative — no bookable slot tokens. It omits pagination/rate-limit behavior, so not 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?

Two sentences, front-loaded with purpose, then return contents, then the sibling routing caveat. No filler.

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, so the description reasonably carries the return-field burden via its enumeration. It covers the key exclusion (slots) and most return fields, though a full field list or pagination note would be more complete.

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 78%, high enough that the schema documents most parameters (date, term, time, view, location, metro_id, party_size). The description adds no parameter syntax beyond what the schema provides, including the important note that date affects ranking but not returned slots. Baseline 3 is appropriate.

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 (Search) and resource (OpenTable restaurants), and lists what comes back. It explicitly distinguishes itself from opentable_find_slots by declaring it does NOT return bookable slot tokens.

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 routing: use opentable_find_slots for a specific venue to check availability, implying this tool is for discovery. The exclusion of slots is stated directly, so the agent knows which sibling to pick.

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

Deploy Server

Other Tools