Event Escapes

build_event_link

Read-onlyIdempotent

Generate a deep link to the Event Escapes event detail page. The user lands on a page where they can review ticket categories, see hotels near the venue (auto-loaded), and complete booking themselves. Optionally pass hotel_id to pin a recommended hotel at the top of the hotels-near-venue list. This does NOT make a reservation; it is purely a navigation aid. For curated packages, use build_package_link instead.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	No	Event slug from search_events results.
`guests`	No	Number of travellers. ASK THE USER before passing this - do not assume a default. Only include if the user has explicitly stated how many people are travelling.
`check_in`	No	Optional check-in date (YYYY-MM-DD) to pre-fill on the page.
`event_id`	No	Event UUID from search_events results.
`hotel_id`	No	Optional hotel ID from search_hotels_near_event. If provided, this hotel will be pinned to the top of the hotels-near-venue list on the event page.
`check_out`	No	Optional check-out date (YYYY-MM-DD) to pre-fill on the page.

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=true, etc.), the description discloses user-facing behavior: landing page shows ticket categories, hotels near venue auto-load, and the user completes booking themselves. It also explains the optional hotel_id pinning effect. This adds contextual richness beyond the safety hints.

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?

The description is well-structured: first sentence states the core purpose, then user experience, optional parameter behavior, and a clear non-reservation caveat. It is front-loaded and every sentence contributes meaning without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 6 parameters and no output schema, the description covers the purpose, user journey, optional parameter effect, and an alternative tool. It fully equips an agent to decide when and how to use it, with no significant gaps given the schema richness.

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 coverage is 100% (all parameters have descriptions), so baseline is 3. The description adds no new parameter-specific meaning beyond what the schema already provides. It mentions hotel_id behavior, but the schema already documents it identically. No extra value is added over the structured definitions.

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 clearly states the tool's function: 'Generate a deep link to the Event Escapes event detail page.' It specifies the resource (deep link to event detail page) and distinguishes it from sibling tools by explicitly naming build_package_link as the alternative for curated packages.

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

Usage Guidelines5/5

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

Provides explicit usage guidance: 'For curated packages, use build_package_link instead' names a direct alternative. It also clarifies when not to use the tool with 'This does NOT make a reservation; it is purely a navigation aid,' setting clear expectations for navigation vs. booking scenarios.

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

All Event Escapes tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool targets a distinct resource or action: events, packages, experiences, hotels, and link building for events vs packages. The descriptions explicitly cross-reference to prevent confusion, such as 'Use build_package_link instead' and 'use search_packages instead'.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: build_event_link, build_package_link, get_event_details, search_events, search_experiences, search_hotels_near_event, search_packages. The verbs (build, get, search) are used predictably.

Tool Count5/5

Seven tools is well within the ideal 3-15 range for a domain. Each tool serves a distinct purpose in the event/package discovery and link-generation workflow, with no redundancy or unnecessary additions.

Completeness4/5

The tool set covers the core workflows: searching events, getting event details, searching hotels and experiences, searching packages, and generating links for both events and packages. A minor gap is the lack of a get_package_details tool to retrieve package details programmatically, but agents can work around it by sending users to the package page.

Resources

Need Help?