Skip to main content
Glama

intentlink

by io.github.whalefuntech

search_events

Search live ticketing/events (concerts, sports, theater) and get ranked event bundles.

Only query is required — a natural-language description of what the buyer wants (e.g. "taylor swift concert near LA this summer"). Add fields to narrow results:

  • keywords: exact terms — performer / team / show / venue (a precise lookup).

  • categories: e.g. ["Concerts"|"Sports"|"Theater"] (read the events://categories resource for valid values).

  • city / state: location (e.g. city="Los Angeles", state="CA"). country defaults to US.

  • date_from / date_to: explicit date window, YYYY-MM-DD (event dates are date-only).

  • when: fuzzy time — "this_weekend" | "this_week" | "this_month" | "next_7_days" | "next_30_days" (ignored if date_from/date_to are given).

  • min_price / max_price: ticket 'from' price band (USD).

  • sort: "relevance" (default) | "soonest" | "cheapest".

  • limit: max results (default 10).

agent_id is REQUIRED: your registered, active agent id — the attribution + access key. A missing/blank or unregistered agent_id is rejected (no anonymous use).

Returns {count, message, events:[{bundle_id,title,venue,city,next_date,price_min,..., sessions:[{date,price,buy_url,landing_url}]}]}. Each session's buy_url is ALREADY the trackable ticket link — hand it to the buyer directly. landing_url is the plain event page. When a date filter is given, sessions are the in-window dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
sortNo
whenNo
limitNo
queryYes
stateNo
date_toNo
agent_idYes
keywordsNo
date_fromNo
max_priceNo
min_priceNo
categoriesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a structured response with event bundles and sessions, notes that 'buy_url' is a direct trackable link, and explains error behavior (rejected if agent_id missing). It does not mention rate limits or side effects, but as a read-only search, this is adequate.

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?

The description is well-structured with a summary paragraph followed by bullet-style parameter explanations. It is approximately 20 lines, which is appropriate given the number of parameters. Some minor redundancy (e.g., stating 'only query is required' and later 'agent_id is REQUIRED') but overall efficient.

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?

Given the tool has 13 parameters and an output schema, the description covers all essential aspects: input parameters, required vs optional, default values, behavior of date filters, and the structure of the response (count, message, events with sessions). It does not address error handling beyond agent_id rejection or pagination, but these are not critical for a search tool with a limit parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The JSON schema has 0% description coverage, so the description must explain all parameters. It does so thoroughly: each parameter (query, keywords, categories, city, state, date_from, date_to, when, min_price, max_price, sort, limit, agent_id) is described with examples, valid values, or behavior (e.g., 'when is ignored if date_from/date_to are given'). This far exceeds minimal compensation.

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 searches 'live ticketing/events (concerts, sports, theater)' and returns 'ranked event bundles'. The verb 'search' and resource 'events' are unambiguous. It distinguishes from siblings (search_products, search_travel) by focusing specifically on events.

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 explains that only 'query' is required, provides guidance on when to use each optional parameter (e.g., 'keywords' for precise lookup, 'when' for fuzzy time), and stresses that 'agent_id' is required. It does not explicitly contrast with sibling tools but the context makes clear this is for event searches.

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

All intentlink toolsInspect
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.6/5.0
Disambiguation5/5

Each tool targets a distinct domain: events, products, and travel. Their purposes are clearly differentiated, with no overlap or ambiguity.

Naming Consistency5/5

All three tools follow a consistent 'search_<domain>' pattern (search_events, search_products, search_travel), making it easy to infer functionality from the name.

Tool Count4/5

Three tools is a small set, but it covers the primary domains (events, shopping, travel) that the server is designed for. It is well-scoped and not overly sparse.

Completeness4/5

The server provides comprehensive search for three major categories. While additional categories could be added, the current set handles common use cases. The descriptions include filtering, pagination, and direct buy links, leaving no obvious dead ends.

Resources