FrontRowTickets.com MCP Server

get_seat_options

Read-onlyIdempotent

Return actual seat listings for one event — section, row, quantity, seat range, base and all-in price per ticket, listing notes, and fee detail — cheapest all-in first. Use after search_events when the user wants seat options to choose from, not just a starting price. max_price caps the ALL-IN price per ticket (fees included); min_quantity keeps only listings with at least that many tickets together. quantity is a filter only, not a reservation or hold. IMPORTANT: always relay each option's notes to the buyer before recommending it — notes carry critical facts (obstructed or limited view, behind-stage seats, parking-only passes that do not include admission, mobile-entry requirements, and delivery dates). Notes pass through verbatim and must never be summarized away. Purchase still happens through the event page link (url) — this tool does not transact.

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

Input Schema

Name	Required	Description
`sort`	No	Sort order: "cheapest" (default, lowest all-in first). "best_value" is not available yet.
`count`	No	Max seat options returned (default 5, max 20)
`event_id`	Yes	Event ID from search_events
`max_price`	No	Hard cap in USD on the ALL-IN price per ticket (fees included)
`min_quantity`	No	Minimum tickets together in one listing (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the default ordering (cheapest all-in first), that max_price is computed on all-in price including fees, and that notes pass through verbatim and must be relayed. The non-transacting nature and the filter-not-reservation caveat are exactly the behavioral facts annotations cannot convey.

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 and ordering come first, followed by parameter clarifications, then the notes/purchase caveat — well front-loaded. It is dense, and the IMPORTANT block is long, but each sentence carries distinct guidance rather than repetition.

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?

There is no output schema, yet the description enumerates the returned fields (section, row, quantity, seat range, base and all-in price, notes, fee detail) and explains the notes field's criticality. Nothing material an agent needs to call or interpret this tool is missing.

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 100%, so the baseline is 3, but the description adds real meaning: max_price caps the ALL-IN price with fees, min_quantity means 'tickets together in one listing,' and quantity is emphasized as a filter, not a hold. These clarifications go beyond the schema's phrasing.

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 verb and resource ('Return actual seat listings for one event') and enumerates the returned fields. It explicitly distinguishes itself from search_events, which only gives a starting price, so an agent can route between the two without opening either 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 an explicit trigger ('Use after search_events when the user wants seat options to choose from') and names the sibling it follows. It also sets boundaries — quantity is a filter not a hold, and purchasing happens via the event page url, not this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FrontRowTickets.com MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?