@striderlabs/mcp-opentable

opentable_check_availability

Check available reservation time slots at a restaurant for a specific date, time, and party size to find open dining times.

Instructions

Check available reservation time slots for a restaurant on a specific date and party size.

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": {
      "restaurantId": "<restaurantId>",
      "date": "<date>",
      "time": "<time>",
      "partySize": "<partySize>"
    },
    "name": "opentable_check_availability"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Date to check in YYYY-MM-DD format
`time`	Yes	Preferred time in HH:MM format (e.g. '19:00'). Availability is shown for nearby times.
`partySize`	Yes	Number of guests
`restaurantId`	Yes	The restaurant ID or profile URL

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.5Jul 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It conveys a read-only intent via 'check,' but it does not explicitly state that no reservation is created, or describe auth, error, or empty-result behavior. It is minimally adequate but not rich.

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?

The description is a single sentence with no filler, front-loaded with the action. Every word contributes to understanding the tool's purpose.

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?

The action and required parameters are adequately documented, but there is no output schema and the description does not clarify the return shape or how this step relates to making or viewing reservations. Adequate for a simple lookup but leaves some context implicit.

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 the baseline is 3. The description adds no parameter-specific detail beyond the schema; it only reiterates date and party size as scoping context.

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 identifies a specific verb ('check') and resource ('available reservation time slots') with clear scope: restaurant, date, and party size. It clearly distinguishes this from sibling tools like opentable_make_reservation and opentable_get_reservations.

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 guidance on when to use this tool versus alternatives, such as using opentable_get_reservations to view existing bookings or opentable_make_reservation after selecting a slot. Usage is only implied by the verb 'check'.

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

Deploy Server