Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opentable_restaurant

Fetch a restaurant's profile and real-time bookable timeslots by ID, date, time, and party size to check availability, cuisines, hours, price band, and reviews.

Instructions

Get an OpenTable restaurant's profile and live availability. Returns a restaurant's profile (location, cuisines, hours, price band, review summary) plus real-time bookable timeslots for the given date/time and party size.

Input Schema

NameRequiredDescriptionDefault
date_timeNoReservation date/time, RFC3339-minute local format; defaults to now
party_sizeNoParty size, default 2
restaurant_idYesOpenTable restaurant id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It helpfully describes the return payload (profile fields plus live timeslots), but does not disclose operational traits such as permissions, rate limits, or whether availability can be empty. The description is useful but not complete for a no-annotation tool.

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 the core purpose, and the second sentence efficiently explains the return content. Every sentence earns its place with no 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?

There is no output schema, so the description appropriately lists the key returned profile fields and mentions live timeslots. Given the low complexity and full schema coverage for inputs, it is largely complete, though it could do more to prepare the agent for empty or unavailable timeslots.

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%, so the schema already documents all three parameters. The description reinforces that date_time and party_size affect live availability, but adds no syntax or format meaning beyond the schema, making 3 the baseline.

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 gives a specific verb and resource: 'Get an OpenTable restaurant's profile and live availability.' It is clearly distinct from sibling tools like opentable_search, opentable_restaurant_menus, and opentable_restaurant_reviews, since it covers both profile detail and real-time bookable timeslots.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the date/time and party-size context and by the availability output, but there is no explicit when-to-use guidance or alternatives. It does not tell the agent when to choose this over opentable_search or the menu/review siblings.

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