Skip to main content
Glama

Venue seating layout

get_venue_layout
Read-onlyIdempotent

One venue's seating layout from UPFRONT's 3D model of it: every section by level, where each sits, how far its front and back are from the field, court or stage (distanceFt: [front, back]), how high they sit (heightFt: [front, back]), whether it's covered (a deck or roof overhead reaching well past the seats; wind can still blow rain in), the sections next to it, and its page. Matches questions like "how is the upper level at Lumen Field laid out?" or "which sections at MetLife are covered?". One venue per answer, with no row or seat counts.

venue: the venue's name ("Madison Square Garden", "MSG", "Lumen Field"). level: optional; one level only ("300 Level", "Upper Level").

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

Input Schema

NameRequiredDescriptionDefault
levelNo
venueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description correctly spends its words elsewhere: the coverage boundary (only venues with an UPFRONT seating chart), the fallback behavior for uncovered venues, and a non-obvious semantic caveat that 'covered' means a deck or roof overhead and does not imply rain protection. That caveat is genuine value beyond structured fields.

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?

Front-loaded with what is returned, then example questions, then per-parameter notes, then coverage limits — a sensible order. Some of the field enumeration ('the sections next to it, and its page') is dense but each item carries real meaning. A few sentences run long but none are filler.

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

Completeness4/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 must describe the return shape and it does thoroughly, including the [front, back] tuple convention for distanceFt and heightFt. Two parameters are both explained despite 0% schema coverage. The only gaps are behavioral edge cases: what happens with an unrecognized level string, and whether the fallback venue list is paginated.

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 full burden, and it does: venue is described as a name with alias tolerance ('Madison Square Garden', 'MSG', 'Lumen Field'), and level is marked optional with the constraint that only one level may be given, with example values ('300 Level', 'Upper Level'). It does not say whether level matching is fuzzy or case-sensitive, which is the remaining ambiguity.

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 names a specific verb+resource (one venue's seating layout) and enumerates the exact payload: sections by level, distanceFt/heightFt ranges, covered flag, adjacent sections, and page. It also bounds scope explicitly ('one venue per answer, with no row or seat counts'), which separates it from a generic seating-map or section-lookup tool without needing the sibling schema.

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 made concrete through two sample questions ('how is the upper level at Lumen Field laid out?', 'which sections at MetLife are covered?') plus the level filter case, so an agent knows the shape of queries this answers. It also states the negative case — venues without an UPFRONT chart return a message listing covered venues. It stops short of naming an alternative sibling for those non-covered cases.

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