Skip to main content
Glama

Seat Map

get_seat_map
Read-only

The venue seating chart for one event, as an image -- 'where is section 104?', 'show me the map'. It is the venue layout, showing where each section sits in the building, and not a photograph of the view from a seat. Some venues have no chart; the section and row from get_ticket_listings still identify the seats. event_id comes from search_events, search_market or get_event_details. No sign-in needed.

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

Input Schema

NameRequiredDescriptionDefault
event_idYesEvent identifier from search_market, search_events or get_event_details.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: the payload is an image, some venues have no chart, and no sign-in is required. It stops short of saying what the agent actually receives when no chart exists (error vs empty result), which is the one behavior an agent would still have to discover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Four sentences, each load-bearing: identity and format first, then the disambiguating exclusion, then the no-chart fallback, then parameter provenance and auth. No filler or hedging.

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 single-parameter read tool with an output schema and full annotation coverage, this covers everything an agent needs: what it returns, when to call it, when not to, what to do if it cannot answer, and that no authentication is needed.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains event_id fully. The description's provenance note (search_events, search_market, get_event_details) largely restates the schema field description, adding no new format or constraint details.

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 resource and format — the venue seating chart for one event, delivered as an image — and immediately contrasts it with what it is not (a photograph of the view from a seat). An agent can distinguish it from get_ticket_listings and get_venue_details without opening a 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?

Gives concrete trigger phrasing ('where is section 104?', 'show me the map'), an explicit exclusion (not a seat-view photo), and a fallback path when the tool cannot serve — venues without a chart, where section and row from get_ticket_listings still identify seats. It also tells the agent where event_id originates.

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