Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

resy_restaurant

Retrieve a Resy restaurant's profile by ID, including name, cuisine, price range, rating, reviews, address, and contact info.

Instructions

Get a Resy restaurant's profile. Returns a Resy restaurant's profile by the required restaurant_id: name, cuisine, price_range (1 to 4), rating, review count, address, neighborhood, coordinates, phone, website, menu URL, party size limits, description, why_we_like_it, need_to_know and images. location_code is a short city identifier.

Input Schema

NameRequiredDescriptionDefault
restaurant_idYesResy restaurant id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does well: it is clearly a read-only lookup and it discloses the returned payload in detail (rating, review count, coordinates, party size limits, why_we_like_it, images). It omits failure behavior for an invalid id and any rate/permission context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the middle sentence is an undifferentiated field dump and the trailing `location_code` sentence is wasted space on a tool that takes no location parameter. Two sentences would have done the job.

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 documenting the returned fields is genuinely necessary and mostly done. Only the stray `location_code` reference and the absence of behavior on a missing/invalid id keep it short of 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 100% and there is only one parameter, so the schema already explains `restaurant_id`. The description actually adds confusion rather than meaning by defining `location_code` as a short city identifier when no such parameter exists on this tool.

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 and resource ('Get a Resy restaurant's profile') keyed to a required `restaurant_id`, and enumerates what comes back. It does not distinguish itself from siblings like resy_search or opentable_restaurant, so an agent must infer that this is the detail-fetch called after a search.

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 only implied: fetching a profile by id presupposes the id came from resy_search, but the description never says so or names alternatives. No when-not-to-use or prerequisite guidance is given.

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