Skip to main content
Glama
chrischall

opentable-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

opentable_list_reservations

Read-only

Retrieve your OpenTable reservations, defaulting to upcoming, with security tokens to cancel or modify each booking. Use scope to include past or all.

Instructions

List the authenticated user's OpenTable reservations. Defaults to upcoming; pass scope="past" or scope="all" to broaden. Each entry includes the security_token needed to cancel or modify.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
scopeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.14.3

TDQS

A3.8/5.0
Behavior3/5

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

Annotations only declare readOnlyHint=true, and the description adds the detail that each entry includes a security_token needed for cancel/modify, which is useful. It does not disclose pagination, limits, or error behaviors, but the safety profile is covered by annotations and the core data shape is hinted.

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 description is concise and front-loads the core purpose and default behavior. It adds key details about scope and the security_token in just two sentences. The schema's 'view' description is verbose but belongs to the schema, not the description.

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?

Given the tool's simple read-only nature, the description covers the essential context: what is returned (reservations, including security_token) and how to control scope. No output schema exists, so the return format is hinted but not exhaustive; however, for a list operation this is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, and the description adds meaning to 'scope' by explaining its values and default. The 'view' parameter is fully documented in the schema, so the description doesn't need to add more. This compensates well for the uncovered parameter.

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?

The description clearly identifies the action (list), the resource (the authenticated user's OpenTable reservations), and explicitly differentiates from siblings such as opentable_search_restaurants or opentable_get_profile. It does not name a direct sibling for listing other entities, but the scope is unambiguous.

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?

The description explains the default behavior (upcoming) and instructs how to broaden with scope, providing clear usage guidance. It does not explicitly state when not to use this tool relative to siblings, but the context is sufficient for typical listing scenarios.

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