Skip to main content
Glama

Search Events

search_events
Read-only

Find events in XP's catalog (concerts, sports, theater, comedy) by performer, team, venue, city or keyword, with optional date, metro and genre filters -- 'shows near me this weekend', 'Taylor Swift tour dates'. Returns event cards with an all-in price preview. search_market runs the same search and adds what each event is trading at; search_performers and search_venues find a performer or venue on its own.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
cbsaNoMetro area filter (synonyms: city, near me, area). ISO US CBSA code or name.
genreNoGenre filter.
limitNoMaximum number of events to return.
queryYesNatural language event search query.
max_dateNoFilter events on or before this date (YYYY-MM-DD). For relative phrases like 'this weekend' or 'next month', resolve against _meta.context.today.
min_dateNoFilter events on or after this date (YYYY-MM-DD). For relative phrases like 'this weekend' or 'next month', resolve against _meta.context.today.
include_scoresNoInclude similarity scores for debugging.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: results are 'event cards with an all-in price preview', telling the agent the shape and pricing basis of the response. It stops short of discussing the 1000-item limit ceiling or result ordering, which keeps it off a 5.

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?

Three sentences, front-loaded with the operation and its scope, followed by illustrative examples and a sibling-routing clause. Every sentence carries distinct information and none repeats the name or title.

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 read-only search over a public catalog with a full-coverage schema and a declared output schema, this covers everything needed: what is searchable, what filters exist, example phrasings, and which sibling to use instead. Return values need not be elaborated because an output schema exists, and the brief 'event cards with an all-in price preview' note is a bonus rather than a required piece.

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 100%, so the baseline is 3; the description earns one above it by explaining that the query is the primary search surface (performer/team/venue/city/keyword) while date, metro and genre are optional narrowing filters, which clarifies how query and filters should be combined. It does not restate the date format or limit bounds, but the schema already handles those.

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 and resource — 'Find events in XP's catalog' — then enumerates the search keys (performer, team, venue, city, keyword) and the optional filters. It also names the three sibling searches and states how each differs, so an agent can pick this tool without opening any schema.

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?

Concrete example queries ('shows near me this weekend', 'Taylor Swift tour dates') anchor when to reach for this tool, and the closing sentence routes explicitly: 'search_market runs the same search and adds what each event is trading at; search_performers and search_venues find a performer or venue on its own.' That is an explicit alternative with the condition that selects each.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources