Skip to main content
Glama

Read the Market

get_market_read
Read-only

What one event is trading at on XP -- 'how much are tickets?'. By seat level, floor first: each level's get-in, then each section's rows front to back, a row shown only when it is cheaper than every row in front of it. Prices are all-in per ticket at the party size (quantity). fan_listings counts the fan listings open to offers on the event; their asks are not included. Clubs, suites, obstructed-view and standing-only seats are left out and named in left_out; get_ticket_listings includes them. event_id comes from search_events or search_market.

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_market_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent identifier from search_market or search_events.
quantityNoParty size; filters to groups a buyer can actually transact at.
sectionsNoSection names the user named, to report on specifically.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare this is a safe read (readOnlyHint/openWorldHint/destructiveHint), but the description adds substantial behavior the annotations cannot carry: prices are all-in per ticket at the party size, fan_listings is a count whose asks are excluded, and clubs/suites/obstructed/standing are omitted and enumerated in left_out. That is exactly the contextual disclosure an agent needs to interpret results correctly.

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?

The core purpose is front-loaded and every sentence carries information about pricing semantics, exclusions, or data provenance. The row-visibility rule ('a row shown only when it is cheaper than every row in front of it') is dense explanation of output content that a shipped output schema partly covers, making the definition slightly longer than strictly necessary.

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 three-parameter read tool with full schema coverage and an output schema, the description covers what an agent still needs: the data source for the required id, how party size affects reported prices, what the fan_listings number means, and how excluded inventory is surfaced. Nothing material for correct selection or invocation 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%, so the baseline is 3, but the description adds genuine meaning for quantity by tying it to the all-in per-ticket price computation, which the schema only frames as 'filters to groups a buyer can actually transact at.' It adds nothing for sections beyond what the schema already says, so it falls short of a 5.

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?

The description uses a specific verb and resource — what a single event is trading at, framed as 'how much are tickets?' — and immediately differentiates itself from get_ticket_listings, which covers the clubs/suites/obstructed/standing categories this tool leaves out. An agent can tell the two apart without opening either 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?

It states the triggering user question ('how much are tickets?'), names the alternative for excluded seat classes (get_ticket_listings includes them), and tells the agent where event_id comes from (search_events or search_market). Explicit when-to-use plus an explicit routing alternative.

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