Gondola Award Travel Search

search_events

Read-only

Search for live events by artist, team, show, or event name. Returns factual event discovery details in provider order, including dates, venue, status, optional approximate listed price range, and the canonical event page. Prices are provider-supplied discovery metadata, not live offers. Use page=0 first and increment page when more results are available. An artist keyword is resolved to that performer and the search is pinned to them, so tribute and club nights that borrow a famous name do not crowd out real tour dates. Many place and word names are also band names (Boston, Chicago, Kansas), so if the response names a performer the user did not mean, search again with match_artist=false rather than concluding nothing is happening. When the resolved performer is the one intended and no events are listed, they have no dates matching that search: do not present namesake events as theirs.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`sort`	No		relevance
`limit`	No
`radius`	No
`keyword`	Yes	Artist, team, show, or event name.
`end_date`	No	Latest local event date, YYYY-MM-DD.
`location`	No	Optional city, region, postal code, or natural-language location.
`start_date`	No	Earliest local event date, YYYY-MM-DD.
`radius_unit`	No		miles
`match_artist`	No	Resolve keyword to a canonical performer before searching. Set false for keywords that are not a performer, such as a genre, venue, or festival name.
`attraction_id`	No	Optional provider performer id. Pins results to that performer exactly.
`classification`	No	Optional segment, genre, or subgenre.
`include_unavailable`	No	Include cancelled and postponed events, excluded by default. Off-sale events are always returned, since they are real dates that are sold out or not yet on sale.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description richly discloses behavior: prices are provider-supplied discovery metadata rather than live offers, artist keywords are pinned to a canonical performer so tribute acts do not crowd out real dates, and namesake ambiguity is explicitly called out. It also warns against presenting namesake events as the user's intended performer's dates, which is valuable behavioral context for an AI agent.

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 dense but every sentence earns its place, covering purpose, return contents, pricing semantics, pagination, and ambiguity handling. It is front-loaded with the core purpose and return details before diving into edge cases, and there is no filler or 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?

Given an output schema exists, the description does not need to explain return structures in full, but it still covers the most important operational concerns: pagination, metadata semantics, artist resolution, and the no-results interpretation. The tool is complex with 13 parameters, yet an agent has enough guidance to call it correctly and interpret results safely.

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 description coverage is 62%, and the description adds meaning beyond the schema by explaining how keyword resolution works, how match_artist=false changes behavior, and how pagination with page=0 should be used. This compensates for the parameters that have no schema description, though it does not exhaustively cover every parameter.

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 opens with a specific verb+resource pair, 'Search for live events by artist, team, show, or event name,' which makes the tool's purpose immediately clear. It also specifies what is returned, including dates, venue, status, price range, and canonical event page, and the domain is distinct from the hotel/flight/vehicle 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 Guidelines4/5

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

The description gives explicit operational guidance: start with page=0 and increment for more results, and search again with match_artist=false when the resolved performer is not the user's intent. It does not explicitly contrast with sibling alternatives, but the event domain is clearly established and no direct event-search sibling exists, so the context is sufficient.

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

All Gondola Award Travel Search 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.2/5.0

Disambiguation5/5

Each tool targets a distinct resource and action; no two tools have overlapping purposes. For example, search_hotels, get_hotel_details, get_hotel_reviews, and get_hotel_stats all address different aspects of hotel research.

Naming Consistency5/5

Tool names follow consistent patterns: search_ for searches, get_ for retrievals, book_ for bookings, and a few standalone verbs like cancel_, create_, delete_. All use snake_case with no mixing of conventions.

Tool Count4/5

With 31 tools, the server is on the high side but covers a broad domain (hotels, flights, vehicles, loyalty, payments). Most tools are justified, though a few hotel analysis tools could potentially be consolidated.

Completeness3/5

Hotels and vehicles have near-complete lifecycle coverage (search, details, book, manage), but flights are missing a book_flight tool, and hotel cancellation is not present. These gaps limit completeness.

search_events

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources