Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

resy_locations

List Resy operating locations (cities) and filter them by free-text substring or country to find the correct location code for restaurant, cuisine, event, and search queries.

Instructions

List Resy's operating locations (cities). Returns Resy's full list of operating locations (cities), optionally filtered by a free-text substring and/or country. This is the discovery source for the location value used throughout the rest of this family (resy-search's/resy-restaurant's location_code, resy-cuisines'/resy-events'/resy-event-detail's location).

Input Schema

NameRequiredDescriptionDefault
qNoCase-insensitive substring match against a location's name, code, or url_slug
countryNoCase-insensitive exact match against a location's country name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/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 burden. It discloses that the full list is returned and that filtering is optional, but says nothing about authentication, rate limits, or result shape beyond the 'cities' framing. Adequate for a simple read-only list, 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.

Conciseness4/5

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

Two sentences, front-loaded with purpose before the routing detail. Slightly redundant, since the first and second sentences both restate 'Resy's operating locations (cities)', but no sentence is wasted.

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 two-optional-parameter list tool with no output schema, the description covers purpose, optional filters, and its role in the tool family. Return-format detail is unnecessary without an output schema, so this is nearly 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 description coverage is 100%, so the schema already documents both parameters in more detail than the description (the schema specifies match against name, code, or url_slug). The description's 'free-text substring and/or country' only restates the schema, so the baseline of 3 applies.

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?

States a specific verb ('List') and resource ('Resy's operating locations (cities)'), and goes further by positioning itself as the discovery source for the location value used by its siblings. An agent can identify this tool's role among resy-search, resy-restaurant, resy-cuisines, and resy-events without opening any schema.

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?

Explicitly says this is the discovery source for the location value used 'throughout the rest of this family', which is strong routing guidance toward the correct tool. It does not state when-not to use it, but the context is unambiguous for a lookup/list tool.

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