Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

resy_search

Find Resy restaurants by name, cuisine, or neighborhood near any location. Optionally check live bookable timeslots for a date and party size—no credentials required.

Instructions

Search Resy restaurants near a location. Searches restaurants by free-text term (name, cuisine, or neighborhood) near a latitude/longitude, optionally including live bookable-timeslot availability for a given date and party size. Credential-free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoReservation date, YYYY-MM-DD; when set, results include live timeslots
sizeNoMax results, default 10
termNoFree-text search term (name, cuisine, or neighborhood)
latitudeYesSearch center latitude
longitudeYesSearch center longitude
party_sizeNoParty size, default 2

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/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. It usefully discloses that the tool is credential-free and that availability is only included when date is set. However, it does not describe the return format, result fields, pagination, or any other behavioral details an agent might need.

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 short and front-loaded with the main action, followed by useful detail and the credential-free note. The first sentence is slightly redundant with the second, but overall there is no wasted content.

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?

For a search tool with no output schema and no annotations, the description covers the core behavior and auth requirement but omits return-value details and does not direct the agent to related tools like resy_restaurant or resy_availability. It is adequate but has clear gaps.

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 mostly paraphrases the schema (free-text term, near latitude/longitude, date and party size) without adding new parameter-level meaning beyond what the schema already provides.

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 ('Search Resy restaurants'), the resource, and the search criteria (free-text term near latitude/longitude). It does not explicitly name or differentiate sibling tools like resy_restaurant or resy_availability, but the free-text/location/availability scope makes the purpose reasonably distinct.

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 gives clear context on when to use this tool: when searching restaurants by free-text term near a location, optionally including live timeslot availability for a date and party size. It does not mention exclusions or alternatives, so it stops short of explicit routing guidance.

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