Skip to main content
Glama

Read a ticket's seat

resolve_seat
Read-onlyIdempotent

A ticket's seat as a seller writes it ("Sec 129C Row 12", "Section 111, Row M, Seats 5-6", "100 Level 113 Row 4") read onto the venue's seating chart: which section and row it is, where the section sits, how far the row is from the field, court or stage, how high it sits, whether it's covered, and a picture of the view. readAs shows how the words were read. A row between the front and back is estimated from them and marked "estimated". A name the chart doesn't know comes back with found false, not a guess.

venue: the venue's name ("Madison Square Garden", "MetLife Stadium"). seat: the seat as the listing gives it.

Covers the venues with an UPFRONT seating chart; for any other venue the answer says so and lists the ones covered.

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": {
      "venue": "<venue>",
      "seat": "<seat>"
    },
    "name": "resolve_seat"
  }
}

Input Schema

NameRequiredDescriptionDefault
seatYes
venueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description is consistent with that. It adds real behavior the annotations cannot convey: readAs exposes the parse, interpolated rows are flagged "estimated", and unknown names return found=false rather than a guess. It could say more about what the returned view picture is (URL vs. rendered image).

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 output is front-loaded before the parameters, and each paragraph has a job (returns, parameters, coverage limit). It is somewhat long and the mid-sentence line breaks make it slower to scan than a tighter block would.

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?

With no output schema, the description enumerates the returned fields (section, row, position, distance, height, covered, view image, readAs, estimated, found) and explains the negative case. For a two-parameter read tool that is complete enough to call and to interpret the result.

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 0%, so the description carries the burden, and it does: venue is illustrated with two real examples and seat is defined as "the seat as the listing gives it" with three sample formats. That meaningfully clarifies both fields, though it does not state whether venue must match a canonical name or how fuzzy matching of the venue string behaves.

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

Purpose4/5

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

The description states a concrete transformation: a free-text seat string ("Sec 129C Row 12") is read onto the venue's seating chart to yield section, row, height, distance, coverage, and a view picture. That is a specific verb+resource. It does not explicitly differentiate itself from siblings like section_info or get_seating_map, so it stops short of a 5.

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

Usage Guidelines4/5

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

It gives a clear applicability condition: it only works for venues with an UPFRONT seating chart, and otherwise reports that and lists covered venues. That is useful when-to-use context, but it names no alternative tool for the uncovered cases, so the routing guidance is incomplete.

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