Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

resy_event_detail

Retrieve a Resy ticketed dining event's description, event-day instructions, and ticket-tier package prices, inclusions, and live availability from prior resy-events slugs; read-only, no purchase.

Instructions

Get a Resy ticketed dining event's full description and ticket packages. Returns a ticketed dining event's full description, event-day instructions, and per-ticket-tier package breakdown (price, what's included, live ticket availability). All three identifiers come from a prior resy-events result: event_url_slug is that result's url_slug, restaurant_url_slug is its restaurant_url_slug, and location is the same city identifier resy-events was called with. Read-only discovery -- does not purchase a ticket.

Input Schema

NameRequiredDescriptionDefault
locationYesResy location code or numeric id, same value resy-events was called with
party_sizeNoParty size, default 2
event_url_slugYesEvent url_slug, from a prior resy-events result
restaurant_url_slugYesRestaurant url_slug, from that same resy-events result's restaurant_url_slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 provided, the description carries the full safety burden and does well: it explicitly labels the tool 'Read-only discovery -- does not purchase a ticket,' clarifying the mutation boundary. It also discloses that ticket availability returned is live. It stops short of stating auth or rate-limit behavior.

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?

Front-loads the core action before the return detail and parameter provenance, which is good ordering. However, the opening 'full description and ticket packages' is then re-stated by the next sentence's returns list, and the parameter-mapping sentence is verbose, so there is some redundancy.

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?

There is no output schema, so the description must describe returns, which it does concretely (description, event-day instructions, per-tier price/inclusions/availability). Combined with the read-only disclosure, it is nearly complete for a detail tool, though permission/auth behavior is unaddressed.

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 baseline is 3. The description largely restates what the schema already documents (event_url_slug from url_slug, restaurant_url_slug from restaurant_url_slug, location as the city identifier), adding coherence but little new syntax or format detail.

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 ticketed dining event), and enumerates what it returns: full description, event-day instructions, and per-ticket-tier package breakdown. It distinguishes itself from the sibling resy-events by positioning itself as the detail tool that consumes a resy-events result.

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?

Clearly explains the prerequisite: all three identifiers must come from a prior resy-events result, and spells out which field maps to which parameter. It gives strong 'when to use' context via the dependency chain, though it stops short of naming when-not-to-use or an alternative detail 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