Skip to main content
Glama

Best seats by view

best_seats
Read-onlyIdempotent

UPFRONT's own listings for one event ranked by where the seats are, not only by price: "best view for 2 under $250", "closest seats to the court for $400 total", "seats in the shade", "not too high up". event_id is UPFRONT's event id (eventId in event results).

prefer: "closest" (nearest the field, court or stage; the default), "lowest" (lowest eye height), "covered" (rows a deck or roof overhead reaches well past, straight up and 30 degrees out toward the field and to either side, first; for shade or rain, though wind can still blow rain in) or "value" (the best mix of closeness and price). quantity: the number of tickets needed together. max_price: per ticket, fees included. max_total_price: the whole group's budget, with quantity. limit: how many picks (default 5, at most 10).

Each pick has the section, row, all-in price (and total for the quantity), the row's distance and height, whether it's covered, the section's view picture (UPFRONT's 3D view, not a photo), its section page, why it was picked, and url, the link to buy exactly that listing.

placed says how many of the matching listings could be put on the seating chart; only those are ranked. hasFacts false means UPFRONT has no seat facts for this venue, so the picks are simply the cheapest and the ranking is by price only. {"error": "search_failed"} means the listings lookup failed, not that nothing is on sale.

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": "best_seats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
preferNoclosest
event_idYes
quantityNo
max_priceNo
max_total_priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / max_price / anyOf
      Previous value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "pattern": "^(?!^[-+.]*$)[+-]?0*\\d*\\.?\\d*$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / max_total_price / anyOf
      Previous value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "pattern": "^(?!^[-+.]*$)[+-]?0*\\d*\\.?\\d*$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "number"
      +  },
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations with real operational detail: only listings that can be placed on the seating chart are ranked (via `placed`), `hasFacts: false` degrades the ranking to cheapest-only, and {"error": "search_failed"} means the lookup failed rather than nothing being on sale. That last distinction is exactly the kind of trap that causes agents to misreport results.

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 is front-loaded and the parameter block follows in a scannable order, with return-value notes last. The `covered` explanation spirals into a long parenthetical about decks, roof angles, and wind-blown rain that is informative but wordier than needed.

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 fully enumerates what each pick contains (section, row, all-in price and total, distance, height, covered flag, 3D view picture, section page, reasoning, buy url). Combined with the degradation and error semantics, an agent can act correctly without guessing.

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 description coverage is 0%, so the description must carry all six parameters — and it does: event_id with a pointer to the source field, all four `prefer` values explained with their defaults, quantity as tickets needed together, max_price as per-ticket with fees included versus max_total_price as the group budget used with quantity, and limit's default of 5 with a cap of 10.

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?

Opens with a specific verb+resource framing — "UPFRONT's own listings for one event ranked by where the seats are, not only by price" — which distinguishes it from price-only siblings like compare_prices and from lookup tools like find_events. The quoted natural-language queries make the intent concrete and unmistakable.

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?

Clearly signals when this tool applies (view-based seat ranking with budget and quantity constraints) and cross-references find_events by telling the agent that event_id is the "eventId in event results." It stops short of naming an explicit alternative for the price-only case or stating exclusions.

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