Skip to main content
Glama

Ticker: Live Event Ticket Market

Event Price Chart

get_event_price_chart
Read-only

Renamed: use get_event_chart with metric "price".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeNoLookback window over snapshot_date: 7d | 14d | 28d | 90d | all (all is bounded to ~1 year). Default 90d. vs only; envelope sources answer full depth.90d
renderNoA rendered chart (a PNG image content block) is included ahead of the data by default. Pass render:false for a data-only (smaller) response.
sourceNoComparison source: vs | tp | tm | tmr | gt | sg | sh | mlb | sgp. vs answers the per-date rollup; every other code answers the per-source series envelope ({source, meta:{coverageStart, lastMeasuredAt, granularity, mapped, bases}, series:[{date, floor, median, p25, p75, floorAip, medianAip, p25Aip, p75Aip, listings, tickets}]}), data only; mapped:false means the event has no link to that source. Default vs (this tool's classic per-date rollup shape); tm is the primary market, tmr the resale market, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale source into one series. Every code serves the price (before fees) in floor and the all-in price (with fees) in floorAip; compare like with like. mlb is the club box office of an mlb game, a primary market of disclosed face values with their disclosed all-in beside them. sgp is the sg primary market; sg is the sg resale market only.vs
event_idYesThe event to chart. Ticker event id, `ev` plus ten characters, as returned by every tool here. A marketplace id also resolves when it carries its source prefix (`vs:`, `tm:`, `tp:`), and a bare marketplace id resolves until 2027-09-13.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / render / description
      Previous value: -"A rendered chart (a PNG image content block) is included ahead of the data by default. Pass false for a data-only (smaller) response."New value: +"A rendered chart (a PNG image content block) is included ahead of the data by default. Pass render:false for a data-only (smaller) response."
    • changedInput schema / properties / source / description
      Previous value: -"Comparison source: vs | tp | tm | tmr | gt | sg | sh | mlb | sgp. Default vs (this tool's classic per-date rollup shape); tm is the primary market, tmr the resale market, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale source into one series. Every code serves the price (before fees) in floor and the all-in price (with fees) in floorAip; compare like with like. mlb is the club box office of an mlb game, a primary market of disclosed face values with their disclosed all-in beside them. sgp is the sg primary market; sg is the sg resale market only."New value: +"Comparison source: vs | tp | tm | tmr | gt | sg | sh | mlb | sgp. vs answers the per-date rollup; every other code answers the per-source series envelope ({source, meta:{coverageStart, lastMeasuredAt, granularity, mapped, bases}, series:[{date, floor, median, p25, p75, floorAip, medianAip, p25Aip, p75Aip, listings, tickets}]}), data only; mapped:false means the event has no link to that source. Default vs (this tool's classic per-date rollup shape); tm is the primary market, tmr the resale market, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale source into one series. Every code serves the price (before fees) in floor and the all-in price (with fees) in floorAip; compare like with like. mlb is the club box office of an mlb game, a primary market of disclosed face values with their disclosed all-in beside them. sgp is the sg primary market; sg is the sg resale market only."
  2. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Comparison source: vs | tp | tm | tmr | gt | sg | sh | mlb | sgp. Default vs (this tool's classic per-date rollup shape); tm is the primary market, tmr the resale market, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale source into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats. mlb is the club box office of an mlb game, a primary market of disclosed face values with their disclosed all-in beside them. sgp is the sg primary market, quoted ALL-IN; sg is the sg resale market only."New value: +"Comparison source: vs | tp | tm | tmr | gt | sg | sh | mlb | sgp. Default vs (this tool's classic per-date rollup shape); tm is the primary market, tmr the resale market, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale source into one series. Every code serves the price (before fees) in floor and the all-in price (with fees) in floorAip; compare like with like. mlb is the club box office of an mlb game, a primary market of disclosed face values with their disclosed all-in beside them. sgp is the sg primary market; sg is the sg resale market only."
  3. Changed2 schema fields changed
    • changedInput schema / properties / source / description
      Previous value: -"Comparison source: vs | tp | tm | tmr | gt | sg | sh | mlb. Default vs (this tool's classic per-date rollup shape); tm is the primary market, tmr the resale market, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale source into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats. mlb is the club box office of an mlb game, a primary market of disclosed face values with their disclosed all-in beside them."New value: +"Comparison source: vs | tp | tm | tmr | gt | sg | sh | mlb | sgp. Default vs (this tool's classic per-date rollup shape); tm is the primary market, tmr the resale market, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale source into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats. mlb is the club box office of an mlb game, a primary market of disclosed face values with their disclosed all-in beside them. sgp is the sg primary market, quoted ALL-IN; sg is the sg resale market only."
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "vs",
      -  "tp",
      -  "tm",
      -  "tmr",
      -  "gt",
      -  "sg",
      -  "sh",
      -  "mlb"
      -]New value: +[
      +  "vs",
      +  "tp",
      +  "tm",
      +  "tmr",
      +  "gt",
      +  "sg",
      +  "sh",
      +  "mlb",
      +  "sgp"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Comparison source: vs | tp | tm | tmr | gt | sg | sh | mlb. Default vs (this tool's classic per-date rollup shape); tm is the primary inventory book, tmr the resale book, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale book into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats. mlb is the club box office of an mlb game, a primary book of disclosed face values with their disclosed all-in beside them."New value: +"Comparison source: vs | tp | tm | tmr | gt | sg | sh | mlb. Default vs (this tool's classic per-date rollup shape); tm is the primary market, tmr the resale market, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale source into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats. mlb is the club box office of an mlb game, a primary market of disclosed face values with their disclosed all-in beside them."
  5. Changed2 schema fields changed
    • changedInput schema / properties / source / description
      Previous value: -"Comparison source: vs | tp | tm | tmr | gt | sg | sh. Default vs (this tool's classic per-date rollup shape); tm is the primary inventory book, tmr the resale book, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale book into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats."New value: +"Comparison source: vs | tp | tm | tmr | gt | sg | sh | mlb. Default vs (this tool's classic per-date rollup shape); tm is the primary inventory book, tmr the resale book, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale book into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats. mlb is the club box office of an mlb game, a primary book of disclosed face values with their disclosed all-in beside them."
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "vs",
      -  "tp",
      -  "tm",
      -  "tmr",
      -  "gt",
      -  "sg",
      -  "sh"
      -]New value: +[
      +  "vs",
      +  "tp",
      +  "tm",
      +  "tmr",
      +  "gt",
      +  "sg",
      +  "sh",
      +  "mlb"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / source / description
      Previous value: -"Comparison source: vs | tp | tm | tmr | gt | sg | sh. Default vs (this tool's classic daily-rollup shape); tm is the primary inventory book, tmr the resale book, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale book into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats."New value: +"Comparison source: vs | tp | tm | tmr | gt | sg | sh. Default vs (this tool's classic per-date rollup shape); tm is the primary inventory book, tmr the resale book, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale book into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats."
  7. Changed2 schema fields changed
    • changedInput schema / properties / source / description
      Previous value: -"Comparison source: vs | tp | tm | tmr | gt | sg. Default vs (this tool's classic daily-rollup shape); tm is the primary inventory book, tmr the resale book, and vs, tp, tmr, gt and sg are all resale. Never mix a primary and a resale book into one series. gt and sg quote ALL-IN prices, so they sit above vs and tp on the same seats."New value: +"Comparison source: vs | tp | tm | tmr | gt | sg | sh. Default vs (this tool's classic daily-rollup shape); tm is the primary inventory book, tmr the resale book, and vs, tp, tmr, gt, sg and sh are all resale. Never mix a primary and a resale book into one series. gt, sg and sh quote ALL-IN prices, so they sit above vs and tp on the same seats."
    • changedInput schema / properties / source / enum
      Previous value: -[
      -  "vs",
      -  "tp",
      -  "tm",
      -  "tmr",
      -  "gt",
      -  "sg"
      -]New value: +[
      +  "vs",
      +  "tp",
      +  "tm",
      +  "tmr",
      +  "gt",
      +  "sg",
      +  "sh"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / range / description
      Previous value: -"Lookback window over snapshot_date: 7d | 14d | 28d | 90d | all (all is bounded to ~1 year). Default 90d. vs only — envelope sources answer full depth."New value: +"Lookback window over snapshot_date: 7d | 14d | 28d | 90d | all (all is bounded to ~1 year). Default 90d. vs only; envelope sources answer full depth."
  9. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already state readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds nothing about deprecation status, whether calling it still functions, or what happens if an agent invokes it, which is the key behavioral fact for a renamed tool.

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?

One short, front-loaded sentence with no wasted words. It is concise, though it omits essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a renamed/deprecated tool with four parameters and no output schema, the description is inadequate. It does not say whether this tool is still callable, whether it forwards to get_event_chart, or what the replacement's required parameters are (e.g., that get_event_chart also requires event_id and a metric argument).

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%, so the schema already fully documents event_id, range, render, and source. The description adds no parameter semantics beyond the implicit equivalence to get_event_chart(metric="price"). Baseline 3 is appropriate.

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

Purpose2/5

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

The description only says the tool was renamed and points to get_event_chart with metric "price". It does not state what the tool actually does (produce a price chart for an event), so an agent unfamiliar with the rename has to infer purpose from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implicitly tells the agent to prefer get_event_chart with metric "price" instead of this tool, which is useful routing. But it gives no explicit when-to-use/when-not guidance and does not address whether this tool still works or is deprecated.

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