Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

resy_events

Get ticketed dining events in a Resy location, revealing fixed-price, fixed-capacity experiences. Supports date and pagination filters for targeted discovery.

Instructions

Get ticketed dining events in a Resy location. Returns ticketed dining events (fixed-price, fixed-capacity experiences a restaurant hosts and sells tickets for, distinct from a regular reservation) in a Resy location. Credential-free, read-only discovery -- does not create, hold, or purchase a ticket.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoOnly return events starting on or after this date, YYYY-MM-DD; defaults to the next calendar day
limitNoMax events returned, default 10
offsetNoPage past the first `limit` events, default 0
locationYesResy location code or numeric id (from a prior resy-search/resy-restaurant response's location_code field)

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?

No annotations are provided, so the description carries the full burden. It explicitly states 'Credential-free, read-only discovery' and clarifies that it 'does not create, hold, or purchase a ticket', which is a strong side-effect disclosure. It does not describe return format or pagination, but for a straightforward discovery tool this is a minor gap.

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?

The description repeats 'ticketed dining events in a Resy location' in both sentences, creating redundancy. The explanatory clause about what ticketed events are is valuable, but could be integrated more concisely.

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?

Given the tool has no output schema and only moderate complexity (4 params, 1 required), the description covers the essential context: what the events are, the read-only nature, and the required location parameter (which is also in the schema). It does not explain return values, but the absence of an output schema makes this less critical for a discovery endpoint.

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%, with all four parameters (location, date, limit, offset) already documented in the schema. The description adds no additional parameter-level meaning, so the baseline score 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?

The description uses a specific verb ('Get') and resource ('ticketed dining events in a Resy location'). It further distinguishes these from regular reservations by defining them as fixed-price, fixed-capacity experiences. This makes the tool's purpose clear even without referencing sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states it is a 'discovery' tool but does not mention alternative tools like resy_search or resy_restaurant, nor does it provide explicit conditions for when to use this tool versus siblings. No exclusion or routing 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