Ticker: Live Event Ticket Market

Event Seat History

get_event_seat_history

Read-only

Renamed: use get_event_seats with view "history".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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".
`limit`	No	Changes per page.
`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.	seat
`since`	No	Oldest change to include, ISO 8601. Omit to reach the seat's first change.
`all_in`	No	Adds each price after fees beside it. On by default; false returns the prices before fees alone.
`cursor`	No	next_cursor from the previous page: one seat's older changes, or the next seats of a section or event read.
`section`	No	Section code, e.g. "104".
`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: +{
+  "default": true,
+  "description": "Adds each price after fees beside it. On by default; false returns the prices before fees alone.",
+  "type": "boolean"
+}

Changed3 schema fields changedOct 15, 2026

changedInput schema / properties / cursor / description

Previous value: -"next_cursor from the previous page, for older changes."New value: +"next_cursor from the previous page: one seat's older changes, or the next seats of a section or event read."

addedInput schema / properties / rows

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

addedInput schema / properties / scope

Added value: +{
+  "default": "seat",
+  "description": "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.",
+  "enum": [
+    "seat",
+    "section",
+    "event"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 10, 2026
- removedInput schema / properties / limit / maximum
```
Removed value: -200
```
First observedOct 2, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already cover the safety profile (readOnlyHint true, destructive false), so the bar is lower, but the description adds only the fact that the tool is renamed. It discloses no behavioral traits such as pagination, truncation, or response shape beyond the redirect.

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?

A single front-loaded sentence with zero waste, which is appropriate for a deprecation notice. It is not padded or buried, though it is terse to the point of omitting any statement of the tool's function.

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?

For a renamed alias, the correct agent behavior is to redirect rather than invoke, and the description accomplishes that despite 11 parameters and no output schema. Nothing further is required for an agent to act correctly, since it should not call this tool at all.

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 100% across 11 parameters, so the schema carries the semantics and baseline 3 applies. The description's only parameter-adjacent claim references a view "history", which does not correspond to any value in the scope enum (seat/section/event) — it is a reference to the successor tool's parameter, not this one's.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what the tool does beyond the name; it only announces a rename. It does effectively differentiate from siblings by pointing to get_event_seats with view "history", so an agent knows this is not the tool to pick. Vague on purpose, clear on routing.

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?

Explicitly tells the agent to use get_event_seats with view "history" instead, which is precisely the when/when-not guidance needed for a deprecated alias. The named alternative and the condition selecting it are both stated, leaving nothing to inference.

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?