Ticker: Live Event Ticket Market

Event Seats

get_event_seats

Read-only

Reserved seats at one event. view live (the default): every seat open now as place indexes with prices, or the seats open at a past moment (at); read count, not the list length. view recent: seats that came on or off sale in the last minutes; republish marks a price change, not a sale. view history: one seat's full history, named by section, row and seat or by place_index; with scope section or event, every seat that changed, as a summary per section or, with rows true, each seat's history a page at a time. Use get_event_sections_live for the house per section. Replaces get_event_seats_live, get_event_seats_recent and get_event_seat_history.

Input Schema

TableJSON Schema

Name	Required	Description
`at`	No	Read the open seats as they stood at this instant, ISO 8601. Omit for now.
`row`	No	Row, e.g. "6".
`rows`	No	scope section or event: each seat's changes, up to 25 seats a page in seat order, instead of the summary. A seat with more than 50 rows is truncated and carries its own next_cursor for scope seat.
`seat`	No	Seat number, e.g. "2".
`view`	No	live (default): open seats. recent: what just moved. history: one seat over time.
`limit`	No	Rows returned. live: seats, default 200, at most 5000. recent: seats, default 50. history: changes per page, default 50, at most 200.
`scope`	No	seat (default): one seat. section: every seat of `section` that changed since `since`. event: every seat of the event that changed. A section or event read answers a summary per section unless `rows` is true.
`since`	No	Oldest change to include, ISO 8601. Omit to reach the seat's first change.
`all_in`	No	Adds each open seat's price after fees and whether it is an estimate, same position as `open`. On by default; false returns the prices before fees alone. Not served with `at`.
`cursor`	No	next_cursor from the previous page: one seat's older changes, or the next seats of a section or event read.
`minutes`	No	How far back to look.
`section`	No	Section code, e.g. "104". recent: only this section. history: the seat's section, with row and seat.
`event_id`	Yes	The event to read.
`place_index`	No	The seat's place index, instead of section, row and seat.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / all_in

Added value: +{
+  "description": "Adds each open seat's price after fees and whether it is an estimate, same position as `open`. On by default; false returns the prices before fees alone. Not served with `at`.",
+  "type": "boolean"
+}

AddedOct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/non-destructive, and the description adds real behavior beyond them: 'read count, not the list length', 'republish marks a price change, not a sale', page/truncation behavior with next_cursor, and that all_in is not served with `at`. These are non-obvious semantics an agent could not infer from annotations or schema alone.

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?

Front-loaded with the live/recent/history modes, then the alternative and the replacement note; no sentence is wasted for a 14-parameter tool. The semicolon-chained clauses are dense and border on run-on, which costs it the top mark but keeps it compact for the complexity involved.

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 high-complexity multi-mode read tool with no output schema, the description covers mode selection, scoping, pagination/truncation, cross-parameter constraints, the sibling alternative, and the consolidation of four tools. Essentially nothing needed to invoke it correctly is missing.

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% with 14 well-documented params, so the baseline is 3, but the description adds interaction semantics the schema does not: how `view`, `scope`, `rows`, `at` and `cursor` combine (e.g. rows turning a per-section summary into per-seat history paged 25 at a time). It stops short of fully mapping every parameter, but meaningfully exceeds the schema.

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 (get) and resource (seats at one event) and enumerates the three operating modes (live/recent/history) with scope. It explicitly distinguishes itself from get_event_sections_live and from the three tools it replaces, so an agent can place it without opening the 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?

Each view mode is given a selection condition ('live: open now', 'recent: came on or off sale in the last minutes', 'history: one seat over time'), and the alternative get_event_sections_live is named with its reason. It also states it replaces get_event_seats_live, get_event_seats_recent and get_event_seat_history, which directly resolves sibling ambiguity.

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 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.

Resources

Need Help?