Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

resy_events

Find ticketed dining events at a Resy location. Discover fixed-price, fixed-capacity restaurant experiences and their dates without creating, holding, or purchasing tickets.

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. Read-only discovery -- does not create, hold, or purchase a ticket.

Input 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?

With no annotations provided, the description carries the full behavioral burden and does so partly: 'Read-only discovery -- does not create, hold, or purchase a ticket' clearly establishes the safety profile an annotation would normally supply. It stops short of pagination, rate-limit, or auth context, but the read-only disclosure is meaningful given the absence of structured hints.

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 opening two sentences are near-duplicates, both stating 'ticketed dining events ... in a Resy location', which wastes space. The parenthetical definition and read-only clause earn their place, but the front-loading is diluted by the redundant restatement.

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 read-only list tool with 100% schema coverage and no output schema, the description is largely complete: it defines the resource, its scope, and its non-mutating nature. It could say more about the return shape or pagination semantics, but nothing critical to invoking it correctly is missing.

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 all four parameters (date, limit, offset, location) are already fully documented with defaults and formats. The description adds no syntax or meaning beyond the schema, making the baseline 3 correct.

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?

States a specific verb ('Get') and resource ('ticketed dining events') scoped to a Resy location, and clarifies the concept as fixed-price, fixed-capacity experiences. It conceptually distinguishes events from a regular reservation, though it never names the actual sibling (resy_event_detail) that would retrieve a single event.

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

Usage Guidelines3/5

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

Usage is implied by 'discovery' and the negative scope 'does not create, hold, or purchase a ticket', which tells the agent this is a read/browse operation. However, it offers no explicit routing to resy_event_detail for a specific event or to resy_search for finding a restaurant, so the agent must infer when this beats its siblings.

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