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. When price_precision is "rank_only" the provider withheld amounts but the ordering is exact, so cite the rank against price_ranked_total ("5th cheapest of 9") and link to the event page for the current price. Never state, estimate, or infer a dollar amount in that case.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`sort`	No	Use "price" for any cheapest-first or budget question. It orders events by their cheapest listing exactly, and each event carries price_rank against price_ranked_total. It is served by a single provider that does no performer resolution, so match_artist has no effect with this sort, and combining it with attraction_id or include_unavailable is rejected rather than silently ignored.	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.
`max_price`	No	Only return events whose cheapest listing is at or below this amount. Requires sort=price, because only the price-ordering provider can filter on price; sending it with any other sort is rejected rather than silently ignored. There is no matching minimum: a price floor is not supported and must not be simulated.
`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

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 2, 2026

addedInput schema / properties / max_price

Added value: +{
+  "description": "Only return events whose cheapest listing is at or below this amount. Requires sort=price, because only the price-ordering provider can filter on price; sending it with any other sort is rejected rather than silently ignored. There is no matching minimum: a price floor is not supported and must not be simulated.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / sort / description

Added value: +"Use \"price\" for any cheapest-first or budget question. It orders events by their cheapest listing exactly, and each event carries price_rank against price_ranked_total. It is served by a single provider that does no performer resolution, so match_artist has no effect with this sort, and combining it with attraction_id or include_unavailable is rejected rather than silently ignored."

changedInput schema / properties / sort / enum

Previous value: -[
-  "relevance",
-  "date",
-  "distance"
-]New value: +[
+  "relevance",
+  "date",
+  "distance",
+  "price"
+]

Changed1 schema field changedAug 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "search_eventsOutput",
+  "type": "object"
+}

Changed3 schema fields changedAug 27, 2026

addedInput schema / properties / attraction_id

Added value: +{
+  "description": "Optional provider performer id. Pins results to that performer exactly.",
+  "type": "string"
+}

addedInput schema / properties / include_unavailable

Added value: +{
+  "default": false,
+  "description": "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.",
+  "type": "boolean"
+}

addedInput schema / properties / match_artist

Added value: +{
+  "default": true,
+  "description": "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.",
+  "nullable": true,
+  "type": "boolean"
+}

Changed37 schema fields changedAug 26, 2026
- removedInput schema / properties / classification / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / classification / default
```
Removed value: -null
```
- addedInput schema / properties / classification / description
```
Added value: +"Optional segment, genre, or subgenre."
```
- removedInput schema / properties / classification / title
```
Removed value: -"Classification"
```
- addedInput schema / properties / classification / type
```
Added value: +"string"
```
- removedInput schema / properties / end_date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / end_date / default
```
Removed value: -null
```
- addedInput schema / properties / end_date / description
```
Added value: +"Latest local event date, YYYY-MM-DD."
```
- removedInput schema / properties / end_date / title
```
Removed value: -"End Date"
```
- addedInput schema / properties / end_date / type
```
Added value: +"string"
```
- addedInput schema / properties / keyword / description
```
Added value: +"Artist, team, show, or event name."
```
- removedInput schema / properties / keyword / title
```
Removed value: -"Keyword"
```
- addedInput schema / properties / limit / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- removedInput schema / properties / location / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / location / default
```
Removed value: -null
```
- addedInput schema / properties / location / description
```
Added value: +"Optional city, region, postal code, or natural-language location."
```
- removedInput schema / properties / location / title
```
Removed value: -"Location"
```
- addedInput schema / properties / location / type
```
Added value: +"string"
```
- addedInput schema / properties / page / minimum
```
Added value: +0
```
- removedInput schema / properties / page / title
```
Removed value: -"Page"
```
- removedInput schema / properties / radius / anyOf
```
Removed value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / radius / default
```
Removed value: -null
```
- addedInput schema / properties / radius / maximum
```
Added value: +500
```
- addedInput schema / properties / radius / minimum
```
Added value: +1
```
- removedInput schema / properties / radius / title
```
Removed value: -"Radius"
```
- addedInput schema / properties / radius / type
```
Added value: +"integer"
```
- removedInput schema / properties / radius_unit / title
```
Removed value: -"Radius Unit"
```
- removedInput schema / properties / sort / title
```
Removed value: -"Sort"
```
- removedInput schema / properties / start_date / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / start_date / default
```
Removed value: -null
```
- addedInput schema / properties / start_date / description
```
Added value: +"Earliest local event date, YYYY-MM-DD."
```
- removedInput schema / properties / start_date / title
```
Removed value: -"Start Date"
```
- addedInput schema / properties / start_date / type
```
Added value: +"string"
```
- removedInput schema / title
```
Removed value: -"search_eventsArguments"
```
- changedOutput schema / (root)
```
Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "search_eventsOutput",
-  "type": "object"
-}New value: +null
```
AddedAug 24, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already include readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds substantive behavioral context beyond annotations: artist keywords are resolved and pinned, tribute/club nights are filtered out, namesake events must not be presented as the performer's own, price_precision 'rank_only' means amounts are withheld and only ranks are exact, and include_unavailable has specific semantics. This is rich behavioral disclosure that helps the agent avoid errors.

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 appropriately sized for a tool with 14 parameters and substantial edge cases. It front-loads the core purpose and return contents, then organizes guidance into clear, purposeful sentences covering pagination, artist resolution, namesake ambiguity, price_precision handling, and provider restrictions. Every sentence earns its place and adds actionable information.

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 search tool with 14 parameters, an output schema, and 71% schema coverage, the description covers the critical operational context: pagination, provider-specific behavior, ambiguous keyword handling, budget-question pricing guidance, and restrictions on parameter combinations. The output schema exists, so return-value details are not required in the description, and all major decision points an agent would face are addressed.

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 coverage is 71%, and the description adds meaningful semantics for key parameters: it explains match_artist resolution behavior, sort=price provider limitations (no performer resolution, rejection when combined with attraction_id/include_unavailable), max_price's requirement for sort=price, and page pagination usage. It doesn't describe every parameter, but it clarifies the non-obvious ones beyond what the schema states.

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 states a specific verb ('Search for live events') and a concrete resource ('by artist, team, show, or event name'), and it distinguishes itself from travel/hotel/vehicle siblings by focusing on event discovery with dates, venue, status, price range, and canonical event page. It clearly communicates what the tool does and its scope.

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?

The description provides explicit usage guidance: use page=0 first, increment page when more results are available; set match_artist=false when the keyword is not a performer; use sort=price for cheapest-first/budget questions; and use max_price only with sort=price. It also names when not to use certain options (e.g., price floor is not supported) and how to handle ambiguous performer names, giving clear alternatives.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.