Skip to main content
Glama

Section facts and view

section_info
Read-onlyIdempotent

What one section of a venue is like: where it is, how far its front and back are from the field, court or stage, how high they sit, which rows are covered (a deck or roof overhead reaching well past every seat in the row, so a row at a deck's front edge isn't; wind can still blow rain in), and a picture of the view from it. Matches questions like "is section 314 at Lumen Field covered?", "what's the view from 210?" or "how high up is row 20 in 111?". It has no row or seat counts.

venue: the venue's name ("Madison Square Garden", "MSG", "Dodger Stadium"). section: the section's name or number as tickets name it ("111", "Section 111", "Field Box 22"). row: optional; one row to describe ("10", "M"). A row between the front and back is estimated from them and marked "estimated".

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

viewPicture is a picture of the view from the section, rendered from UPFRONT's 3D model of the venue (not a photo). sectionPage is the section's page on UPFRONT. source says where the facts come from.

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>",
      "section": "<section>"
    },
    "name": "section_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowNo
venueYes
sectionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, it discloses that viewPicture is rendered from a 3D model rather than a photo, that unnamed rows are interpolated ('estimated'), that coverage is decided by a deck/roof reaching past every seat (with a rain-blown-in caveat), and what happens for uncovered venues. It also names the secondary return fields, sectionPage and source.

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?

Purpose, examples, parameter glossary, and return-field notes are clearly segmented and front-loaded. The covered-row explanation with its wind/rain parenthetical is slightly heavier than needed, but it is the tool's subtlest fact and the placement is sensible.

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 still accounts for the response shape (facts, viewPicture, sectionPage, source) and the coverage-limit branch. For a three-parameter read tool, nothing an agent needs to call it correctly or interpret the answer is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 full burden and does it: venue accepts abbreviations ('MSG'), section accepts the ticket-style name ('111', 'Section 111', 'Field Box 22'), and row is optional with defined estimation behavior when it falls between front and back. This adds meaning well beyond three bare string fields.

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 opens with a specific resource statement: what a section is like, its location, front/back distances to the field/court/stage, height, covered rows, and a view picture. It also explicitly bounds the tool ('It has no row or seat counts'), which separates it from siblings like get_seating_map or venue_info that would carry that data.

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?

Usage is demonstrated with concrete example questions ('is section 314 at Lumen Field covered?', 'how high up is row 20 in 111?') and an explicit exclusion: it only covers venues with an UPFRONT seating chart, and otherwise the answer lists covered venues. It stops short of naming which sibling to call for the out-of-scope cases, so the routing is inferred rather than stated.

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