Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opentable_restaurant_menus

Get an OpenTable restaurant's menus by ID to access structured menu titles, sections, items, prices, and descriptions.

Instructions

Get an OpenTable restaurant's menus. Returns the menus of one OpenTable restaurant, identified by the required restaurant_id. Each menu has a title, a currency and sections, and each section lists items with title, price and description. The price is returned as a string in the menu's currency, for example HK$.

Input Schema

NameRequiredDescriptionDefault
restaurant_idYesOpenTable restaurant id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the full burden and does well: it discloses the return shape (menus with title, currency, sections; items with title, price, description) and the price format as a currency string (e.g. HK$). It is a read operation with no side effects stated, though auth/rate-limit behavior is not covered.

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?

Front-loaded with the core action, followed by the identifier requirement and then the return structure. Four sentences, all informative, with no filler; could be marginally tighter but earns its length given no output schema.

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 single-parameter read tool with no output schema, the description adequately explains what is returned and in what shape, closing the gap left by the missing output schema. The main omission is sibling routing and how to obtain a valid restaurant_id.

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% for the single parameter, so the schema already documents `restaurant_id`. The description reinforces that it is required and identifies the restaurant, but adds no format or sourcing detail beyond the schema. Baseline 3 applies.

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?

States a specific verb+resource: 'Get an OpenTable restaurant's menus', and specifies the required identifier. It is distinguishable from siblings like opentable_restaurant and opentable_restaurant_reviews by the resource (menus), but it never explicitly names or contrasts with those siblings.

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?

The description implies usage by stating the tool needs a `restaurant_id`, but gives no when-to-use guidance, no alternatives (e.g. opentable_restaurant for details, opentable_restaurant_reviews for reviews), and no prerequisites for obtaining the id.

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