Skip to main content
Glama
resy-mcp

resy-mcp

by chrischall

resy_list_reservations

Read-only

Lists your Resy reservations with upcoming, past, or all scopes and returns the token needed to cancel. Use it to review bookings and check cancellability before making changes.

Instructions

List the user's Resy reservations. Defaults to upcoming; pass scope="past" or "all" to broaden. Each result includes the resy_token needed for cancellation, plus occasion/special_request/cancellability.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resy_list_reservations"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNo"full" (default) returns each reservation as JSON; "brief" returns one line per reservation: <venue> <HH:MM>, party of <n> — <YYYY-MM-DDTHH:MM or "no date"> — <booked|past>, inside the untrusted-data envelope as data: string[] (venue names are third-party text); "-- none" when there are none.
scopeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.1
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "\"full\" (default) returns each reservation as JSON; \"brief\" returns one line per reservation: <venue> <HH:MM>, party of <n> — <YYYY-MM-DDTHH:MM or \"no date\"> — <booked|past>, inside the untrusted-data envelope as data: string[] (venue names are third-party text); \"-- none\" when there are none.",
      +  "enum": [
      +    "full",
      +    "brief"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.5.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds substantive context on what comes back — resy_token for cancellation, occasion, special_request, and cancellability. It omits pagination or result-count behavior, which matters for a list tool with no output schema.

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

Conciseness5/5

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

Three short sentences with the list scope front-loaded, the default/variation immediately after, and return-field notes last. Every sentence carries information an agent needs; nothing is padded.

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-parameter read tool with no output schema, the definition covers default scope, alternative scopes, and salient return fields, while the schema handles the brief/full view distinction. The only gap is the absence of any note on result volume or pagination for what could be a long reservation history.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% because the scope parameter has an enum but no description; the description compensates fully by supplying the default (upcoming) and the effect of past/all. The view parameter is thoroughly documented in the schema, so no description-level explanation is needed there.

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 and resource: "List the user's Resy reservations." Among the sibling list_* tools (resy_list_favorites, resy_list_notify, resy_list_payment_methods) the resource "reservations" unambiguously selects this one 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?

Gives clear default behavior ("Defaults to upcoming") and the condition for broadening to past/all, which resolves the main usage decision an agent faces. It stops short of naming alternatives such as resy_cancel for the follow-up action even though it mentions resy_token is returned for cancellation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.