Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

resy_availability

Get a Resy restaurant's bookable reservation timeslots. Returns the bookable reservation timeslots Resy currently shows for a restaurant, date, and party size -- the same read-only availability an anonymous visitor sees before signing in.

Instructions

Get a Resy restaurant's bookable reservation timeslots. Returns the bookable reservation timeslots Resy currently shows for a restaurant, date, and party size -- the same read-only availability an anonymous visitor sees before signing in. The date is optional and defaults to the current date in UTC; the response echoes the date used. This is discovery only; it does not create, hold, modify, or cancel a reservation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoReservation date, YYYY-MM-DD. Defaults to the current date in UTC
party_sizeNoParty size, default 2
restaurant_idYesResy restaurant id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.12
    • changedInput schema / properties / date / description
      Previous value: -"Reservation date, YYYY-MM-DD"New value: +"Reservation date, YYYY-MM-DD. Defaults to the current date in UTC"
    • changedInput schema / required
      Previous value: -[
-  "restaurant_id",
-  "date"
-]New value: +[
+  "restaurant_id"
+]
  2. Addedv1.17.5

TDQS

A4.1/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 burden and does well: it discloses that results are the read-only availability an anonymous visitor sees before signing in (i.e., no auth needed) and that the response echoes the date used. It stops short of describing rate limits, pagination, or what an empty result means for a fully-booked restaurant.

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 operation is stated first, followed by behavioral context and then the scope exclusion, which is good front-loading. The phrase 'bookable reservation timeslots' is repeated in the first two sentences, a minor redundancy that keeps it out of 5 territory.

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, and the description compensates by describing the read semantics and that the date is echoed, which is enough for a 3-parameter lookup. It could still say more about the shape/emptiness of results, so it is not fully 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 restaurant_id, date (YYYY-MM-DD, UTC default), and party_size (default 2). The description mainly restates the date default and its echo in the response, adding only marginal meaning over the schema; baseline 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 (Get) and resource (a Resy restaurant's bookable reservation timeslots), and the second sentence pins the scope to a restaurant/date/party-size read. It is clearly distinguishable from siblings like resy_restaurant or resy_search 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?

The closing sentence gives an explicit when-not ('This is discovery only; it does not create, hold, modify, or cancel a reservation'), which sets a clear usage boundary. It does not name a sibling alternative for non-availability tasks, so it falls short of a 5.

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