Skip to main content
Glama

Ticker: Live Event Ticket Market

by com.findticker
OverviewDiscussionsAdmin

Search Events

search_events
Read-only

Finds events by name, performer, venue or date, and by on-sale, presale or added dates, and gives their event ids. Use screen_events to rank or filter by price, demand or inventory. Rows from other tools already carry event_id and event_url, so do not search again for a link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
limitNoRows per page. A page too large for one tool result comes back as the first rows plus `meta.truncated` and `meta.total_rows`; narrow the search or the dates rather than repeating the call.
queryNoAlias for `search`; prefer `search`. Ignored when `search` is also present.
searchNoRanking words (hottest, best, top, movers) are a sort on screen_events, never search text. NOT A LINK RESOLVER: rows from other tools already carry `event_id` and `event_url`; matching a row by name can land on a different event. Names only: event, performer or venue (min 2 chars), e.g. "taylor swift", "lakers", "Madison Square Garden". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so "Red Sox Yankees" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname ("MSG") before searching. Omit to browse by filters alone; use screen_events to rank.
statusNoFilter by event status. Omit for all statuses; pass 'active' for the live universe. When a filtered search finds nothing it is re-run over every status and the result says retried_including_inactive: true; each row carries currently_priced (false = the event exists but is not priced right now). 'active' for the live universe.
date_toNoEvent date on/before this instant (ISO 8601, offset ok, over utc_date).
sort_byNoSort key. Sorting by onsale_date or presale1_date implicitly filters to events where that date is known (only a minority carry sale dates). Default utc_date.utc_date
venue_idNoRestrict to one venue. Ticker venue id, `vn` plus ten characters. A marketplace id also resolves with its `vs:` prefix, and bare until 2027-09-13.
date_fromNoEvent date on/after this instant (ISO 8601, offset ok, over utc_date).
onsale_toNoPublic on-sale on/before this instant. Events with no known on-sale date are excluded.
created_toNoTicker discovered the event on/before this instant.
presale_toNoFirst presale on/before this instant. Events with no known presale date are excluded.
sort_orderNoDefault asc (soonest first), the natural discovery order. The REST endpoint defaults to desc; this tool flips it.asc
onsale_fromNoPublic on-sale on/after this instant. Events with no known on-sale date are excluded.
created_fromNoTicker discovered the event on/after this instant.
include_pastNoInclude events whose date is already past. Default false (upcoming only). When true without an explicit date_from, results are bounded to the last 90 days.
performer_idNoRestrict to events headlined by one performer. Ticker performer id, `pf` plus ten characters, as returned by every tool here. A marketplace id also resolves with its `vs:` prefix, and bare until 2027-09-13.
presale_fromNoFirst presale on/after this instant. Events with no known presale date are excluded.
monitoring_priorityNoFilter by exact coverage tier (1=high … 10=low).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Rows per page. A page too large for one tool result comes back as the first rows plus `meta.truncated` and `meta.total_rows`; narrow the search or the dates rather than repeating the call."
    • changedInput schema / properties / search / description
      Previous value: -"Names only: event, performer or venue (min 2 chars), e.g. \"taylor swift\", \"lakers\", \"Madison Square Garden\". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so \"Red Sox Yankees\" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname (\"MSG\") before searching. Omit to browse by filters alone; use screen_events to rank."New value: +"Ranking words (hottest, best, top, movers) are a sort on screen_events, never search text. NOT A LINK RESOLVER: rows from other tools already carry `event_id` and `event_url`; matching a row by name can land on a different event. Names only: event, performer or venue (min 2 chars), e.g. \"taylor swift\", \"lakers\", \"Madison Square Garden\". Words match in any order: each word of 3 or more letters must be in the event's name, its performer or its venue, so \"Red Sox Yankees\" finds the game. Joining words (vs, and, the) are ignored. Rows whose name holds every word come first. Not a ranking word (hottest, best, top, movers) and not a typo of one. A venue term returns the events playing there. Venues are stored under their official name, so expand a nickname (\"MSG\") before searching. Omit to browse by filters alone; use screen_events to rank."
  2. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -100
  3. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"Alias for `search` — prefer `search`. Ignored when `search` is also present."New value: +"Alias for `search`; prefer `search`. Ignored when `search` is also present."
    • changedInput schema / properties / sort_order / description
      Previous value: -"Default asc (soonest first) — the natural discovery order. The REST endpoint defaults to desc; this tool flips it."New value: +"Default asc (soonest first), the natural discovery order. The REST endpoint defaults to desc; this tool flips it."
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds non-obvious workflow context: that it hands back event ids and that a name match can be unnecessary when a link already exists. It stops short of describing pagination/truncation behavior at the top level, but that lives in the schema.

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 short sentences, each earning its place: purpose and scope, sibling routing, and a duplicate-work warning. The core capability is front-loaded before the alternative tool is mentioned.

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?

With 19 optional parameters at 95% schema coverage and no output schema, the definition is nearly complete; it states that event ids are returned, partially covering the return surface. It does not, however, hint at pagination or truncation at the top level, leaving that burden entirely to the limit parameter description.

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 description coverage is 95% and the per-parameter descriptions are unusually detailed (search semantics, status retry behavior, sort implications, id formats). The description only restates the filter dimensions, adding essentially nothing beyond what the schema already supplies, so the baseline 3 applies.

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?

States a specific verb (finds) and resource (events), enumerates the searchable dimensions (name, performer, venue, date, on-sale/presale/added dates), and names the return value (event ids). It explicitly separates itself from screen_events, so an agent can route correctly without opening schemas.

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?

Names the alternative (screen_events) and the exact condition that selects it (rank or filter by price, demand, inventory). It also gives a negative rule of thumb — do not re-search for a link when rows already carry event_id and event_url — which is a concrete when-not-to-call case.

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

All Ticker: Live Event Ticket Market toolsInspect
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.

Resources