Skip to main content
Glama

Ticker: Live Event Ticket Market

Get Section Seat Availability

get_event_sections_live
Read-only

Returns open-seat counts per section of one event from the primary market's seat data, now or in the past: every section now with prices and capacity, every section at a past moment, one section over time, general admission sections over time, or every section across a window. Use it when the person asks how many seats are open by section, or how availability changed. For section prices and resale listings use get_event_sections; for single seats use get_event_seats.

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": {
      "event_id": "<event_id>"
    },
    "name": "get_event_sections_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoThe instant to read the house at, ISO 8601. Defaults to now.
viewNonow (default): each section right now, with the lowest, median and highest price, capacity and what left the resale market. at: every section's open count at a past moment, up to 90 days back; read it twice and subtract to see where seats went. series: one section over up to 7 days, in 5m or 1h steps; only the newest point's prices are exact. ga: each general admission section's open count over time; added and removed are changes to the open count. frames: every section's open count at each step of a window; with source mlb, the club's primary market's seat frames, which its seat reads take as frame.
frameNosource mlb only, and required for its seat reads: one of the event's frames, as get_event_sections_live view frames lists them.
limitNonow: sections returned when `sections` is omitted, default 60. ga: points per page, default 200.
sinceNoOldest point to include, ISO 8601. Defaults to 24 hours ago.
untilNoNewest step, ISO 8601. Defaults to now.
widthNoInstead of pages: the shape of the whole history in one answer, as the first, last, lowest and highest point of each of `width` equal slices of time from the section's first observation to now. At most four points a slice. Use it for the shape of a busy section, which can hold tens of thousands of changes.
all_inNoAdds each section's lowest, median and highest price after fees (lowest_aip_price, median_aip_price, highest_aip_price) and whether the lowest is an estimate (aip_estimated). On by default; false returns the prices before fees alone.
bucketNoPoint size: 5m for the last few hours, 1h for days. `open_count` is exact at every bucket. THE PRICES ARE NOT (source tm): they are exact on the newest bucket only; on every earlier bucket they are the seats open now valued at the prices recorded for that bucket, an approximation. Never present an earlier bucket's price as the price at that time.
cursorNonext_cursor from the previous page, for newer points. A page after the first carries the points alone.
sourceNotm (the default) or mlb, a club's primary market. mlb reads one frame at a time: list them with get_event_sections_live view frames and source mlb.
sectionNoseries: the section's section_key, e.g. "104" (required). ga: a general admission section's code, to add its exact points.
currencyNousd or venue. venue answers an event in a Canadian or UK venue with every price in the venue's currency (CAD or GBP) at the event's Bank of Canada rate; one rate converts every market, so the cheapest market and any order stay the same. Omit for USD. A view with no price ignores it. An answer in the venue's currency says currency, venue_currency, fx_rate (USD per one unit of venue_currency) and fx_rate_date; quote the currency with every price and the rate date when it is CAD or GBP. A US event is always USD. mlb_* prices keep mlb_currency.
event_idYesThe event to read.
intervalNoStep size. One too fine for the window is widened, never the window shortened; `interval` says which was served.
sectionsNonow and frames: only these sections, by section_key. Omit for the whole house.
occurrenceNo0 unless the event lists the code twice, as `sections` shows. `section` and `occurrence` together name one section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"usd or venue. venue answers an event in a Canadian venue with every price in CAD at the event's Bank of Canada rate; one rate converts every market, so the cheapest market and any order stay the same. Omit for USD. A view with no price ignores it. An answer about an event in a Canadian venue says currency, venue_currency, fx_rate (USD per one unit of venue_currency) and fx_rate_date; quote the currency with every price and the rate date when it is CAD. A US event is always USD. mlb_* prices keep mlb_currency."New value: +"usd or venue. venue answers an event in a Canadian or UK venue with every price in the venue's currency (CAD or GBP) at the event's Bank of Canada rate; one rate converts every market, so the cheapest market and any order stay the same. Omit for USD. A view with no price ignores it. An answer in the venue's currency says currency, venue_currency, fx_rate (USD per one unit of venue_currency) and fx_rate_date; quote the currency with every price and the rate date when it is CAD or GBP. A US event is always USD. mlb_* prices keep mlb_currency."
  2. Changed1 schema field changed
    • changedInput schema / properties / currency / description
      Previous value: -"usd or venue. venue answers an event in a Canadian venue with every price in CAD at the event's Bank of Canada rate; one rate converts every market, so the cheapest market and any order stay the same. Omit for the account's saved choice (USD unless the person chose venue in Settings). An answer about an event in a Canadian venue says currency, venue_currency, fx_rate (USD per one unit of venue_currency) and fx_rate_date; quote the currency with every price and the rate date when it is CAD. A US event is always USD. mlb_* prices keep mlb_currency."New value: +"usd or venue. venue answers an event in a Canadian venue with every price in CAD at the event's Bank of Canada rate; one rate converts every market, so the cheapest market and any order stay the same. Omit for USD. A view with no price ignores it. An answer about an event in a Canadian venue says currency, venue_currency, fx_rate (USD per one unit of venue_currency) and fx_rate_date; quote the currency with every price and the rate date when it is CAD. A US event is always USD. mlb_* prices keep mlb_currency."
  3. Changed1 schema field changed
    • changedInput schema / properties / view / description
      Previous value: -"now (default), at (a past moment), series (one section over time), ga (general admission over time), frames (every section over a window)."New value: +"now (default): each section right now, with the lowest, median and highest price, capacity and what left the resale market. at: every section's open count at a past moment, up to 90 days back; read it twice and subtract to see where seats went. series: one section over up to 7 days, in 5m or 1h steps; only the newest point's prices are exact. ga: each general admission section's open count over time; added and removed are changes to the open count. frames: every section's open count at each step of a window; with source mlb, the club's primary market's seat frames, which its seat reads take as frame."
  4. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"tm (the default) or mlb, a club box office. mlb reads one frame at a time: list them with get_event_sections_live view frames and source mlb."New value: +"tm (the default) or mlb, a club's primary market. mlb reads one frame at a time: list them with get_event_sections_live view frames and source mlb."
  5. Changed11 schema fields changed
    • changedInput schema / properties / all_in / description
      Previous value: -"Adds each section's lowest, median and highest price after fees and whether the lowest is an estimate. On by default; false returns the prices before fees alone."New value: +"Adds each section's lowest, median and highest price after fees (lowest_aip_price, median_aip_price, highest_aip_price) and whether the lowest is an estimate (aip_estimated). On by default; false returns the prices before fees alone."
    • changedInput schema / properties / bucket / description
      Previous value: -"Point size: 5m for the last few hours, 1h for days. `open_count` is exact at every bucket. THE PRICES ARE NOT: they are exact on the newest bucket only; on every earlier bucket they are the seats open now valued at the prices recorded for that bucket, an approximation. Never present an earlier bucket's price as the price at that time."New value: +"Point size: 5m for the last few hours, 1h for days. `open_count` is exact at every bucket. THE PRICES ARE NOT (source tm): they are exact on the newest bucket only; on every earlier bucket they are the seats open now valued at the prices recorded for that bucket, an approximation. Never present an earlier bucket's price as the price at that time."
    • addedInput schema / properties / currency
      Added value: +{
      +  "description": "usd or venue. venue answers an event in a Canadian venue with every price in CAD at the event's Bank of Canada rate; one rate converts every market, so the cheapest market and any order stay the same. Omit for the account's saved choice (USD unless the person chose venue in Settings). An answer about an event in a Canadian venue says currency, venue_currency, fx_rate (USD per one unit of venue_currency) and fx_rate_date; quote the currency with every price and the rate date when it is CAD. A US event is always USD. mlb_* prices keep mlb_currency.",
      +  "enum": [
      +    "usd",
      +    "venue"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / frame
      Added value: +{
      +  "description": "source mlb only, and required for its seat reads: one of the event's frames, as get_event_sections_live view frames lists them.",
      +  "pattern": "^[0-9a-f]{64}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / interval
      Added value: +{
      +  "description": "Step size. One too fine for the window is widened, never the window shortened; `interval` says which was served.",
      +  "enum": [
      +    "5m",
      +    "15m",
      +    "1h",
      +    "6h",
      +    "1d"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / section / description
      Previous value: -"series: the section's ticket code, e.g. \"104\" (required). ga: a general admission section's code, to add its exact points."New value: +"series: the section's section_key, e.g. \"104\" (required). ga: a general admission section's code, to add its exact points."
    • changedInput schema / properties / sections / description
      Previous value: -"Only these sections, by ticket code (e.g. [\"104\",\"FL2\"]). Omit for the whole house."New value: +"now and frames: only these sections, by section_key. Omit for the whole house."
    • addedInput schema / properties / source
      Added value: +{
      +  "description": "tm (the default) or mlb, a club box office. mlb reads one frame at a time: list them with get_event_sections_live view frames and source mlb.",
      +  "enum": [
      +    "tm",
      +    "mlb"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / until
      Added value: +{
      +  "description": "Newest step, ISO 8601. Defaults to now.",
      +  "format": "date-time",
      +  "type": "string"
      +}
    • changedInput schema / properties / view / description
      Previous value: -"now (default), at (a past moment), series (one section over time), ga (general admission over time)."New value: +"now (default), at (a past moment), series (one section over time), ga (general admission over time), frames (every section over a window)."
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "now",
      -  "at",
      -  "series",
      -  "ga"
      -]New value: +[
      +  "now",
      +  "at",
      +  "series",
      +  "ga",
      +  "frames"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / all_in / description
      Previous value: -"Adds each section's lowest price after fees and whether it is an estimate. On by default; false returns the prices before fees alone."New value: +"Adds each section's lowest, median and highest price after fees and whether the lowest is an estimate. On by default; false returns the prices before fees alone."
  7. Changed11 schema fields changed
    • removedInput schema / properties / all_in / default
      Removed value: -true
    • addedInput schema / properties / at
      Added value: +{
      +  "description": "The instant to read the house at, ISO 8601. Defaults to now.",
      +  "format": "date-time",
      +  "type": "string"
      +}
    • addedInput schema / properties / bucket
      Added value: +{
      +  "description": "Point size: 5m for the last few hours, 1h for days. `open_count` is exact at every bucket. THE PRICES ARE NOT: they are exact on the newest bucket only; on every earlier bucket they are the seats open now valued at the prices recorded for that bucket, an approximation. Never present an earlier bucket's price as the price at that time.",
      +  "enum": [
      +    "5m",
      +    "1h"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "next_cursor from the previous page, for newer points. A page after the first carries the points alone.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / properties / limit / default
      Removed value: -60
    • changedInput schema / properties / limit / description
      Previous value: -"Cap on sections returned when `sections` is omitted. The widest events draw 650 sections; `sections_total` is always the true count."New value: +"now: sections returned when `sections` is omitted, default 60. ga: points per page, default 200."
    • addedInput schema / properties / occurrence
      Added value: +{
      +  "description": "0 unless the event lists the code twice, as `sections` shows. `section` and `occurrence` together name one section.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / section
      Added value: +{
      +  "description": "series: the section's ticket code, e.g. \"104\" (required). ga: a general admission section's code, to add its exact points.",
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "Oldest point to include, ISO 8601. Defaults to 24 hours ago.",
      +  "format": "date-time",
      +  "type": "string"
      +}
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "now (default), at (a past moment), series (one section over time), ga (general admission over time).",
      +  "enum": [
      +    "now",
      +    "at",
      +    "series",
      +    "ga"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / width
      Added value: +{
      +  "description": "Instead of pages: the shape of the whole history in one answer, as the first, last, lowest and highest point of each of `width` equal slices of time from the section's first observation to now. At most four points a slice. Use it for the shape of a busy section, which can hold tens of thousands of changes.",
      +  "maximum": 2000,
      +  "minimum": 50,
      +  "type": "integer"
      +}
  8. Changed1 schema field changed
    • changedInput schema / properties / all_in / description
      Previous value: -"Adds each section's lowest price after fees and whether it is an estimate. On by default; false returns the list prices alone."New value: +"Adds each section's lowest price after fees and whether it is an estimate. On by default; false returns the prices before fees alone."
  9. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -650
  10. Changed2 schema fields changed
    • changedInput schema / properties / all_in / default
      Previous value: -falseNew value: +true
    • changedInput schema / properties / all_in / description
      Previous value: -"True adds each section's lowest price after fees and whether it is an estimate."New value: +"Adds each section's lowest price after fees and whether it is an estimate. On by default; false returns the list prices alone."
  11. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety needs no restating. The description still adds a genuine boundary beyond the annotations: the data is the primary market's seat counts, not resale listings, and covers both current and historical reads. It stops short of disclosing caveats an agent must not miss in output, such as the approximate historical prices and cursor paging, which live only 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with the core purpose front-loaded, then the mode list, then the sibling routing. The mode enumeration is slightly redundant with the `view` enum but still helps selection; nothing is padded or vague.

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 complex 17-parameter tool with no output schema, the description establishes what the tool answers and how it differs from neighbors. It does not describe return shape or paging (next_cursor, pages) or the mlb frame requirement, but the schema covers those thoroughly at 100% coverage, so the gap is minor.

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% and the 17 parameters, including five enums, are documented in detail there; the description's enumeration of the five read modes largely restates the `view` enum. It adds no syntax, defaults, or format guidance beyond the schema, 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 and resource ('Returns open-seat counts per section of one event') plus scope ('from the primary market's seat data') and time coverage ('now or in the past'). It then names the sibling tools it is not, so an agent can distinguish it from get_event_sections and get_event_seats 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?

Explicitly says when to use it ('how many seats are open by section, or how availability changed') and routes two adjacent needs elsewhere: 'For section prices and resale listings use get_event_sections; for single seats use get_event_seats.' Both a positive trigger and named alternatives are present.

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