Skip to main content
Glama
Sign In

FrontRowTickets.com MCP Server

by com.frontrowtickets
OverviewDiscussionsAdmin

search_events

Read-onlyIdempotent

Start here for discovery: search FrontRowTickets.com ticket inventory by free text, city, date range, and category (sports, concerts, theater, comedy). All filters are optional and combine freely; returns up to 'limit' events (default 10, max 50, no further pages), soonest first, with ticket counts and starting prices. Use get_event for one event's full record, get_deals when the user has a hard budget cap.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name, e.g. Chicago
limitNoMax results returned (default 10, max 50)
queryNoFree text: team, artist, show, or venue name
date_toNoLatest event date (ISO)
categoryNoOne of sports, concerts, theater, comedy
date_fromNoEarliest event date (ISO)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / date_to / $ref
      Removed value: -"#/properties/date_from"
    • addedInput schema / properties / date_to / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}"
    • addedInput schema / properties / date_to / type
      Added value: +"string"
  2. Changed2 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"One of sports, concerts, theater, comedy"
    • addedInput schema / properties / limit / description
      Added value: +"Max results returned (default 10, max 50)"
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing result ordering (soonest first), the pagination ceiling (default 10, max 50, no further pages), and what each result carries (ticket counts and starting prices). The 'filters combine freely' note tells the agent the query model is conjunctive, which the annotations do not cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, all front-loaded: what it searches, how filters and results behave, then sibling routing. No filler and no restatement of the tool name.

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 carries the return-shape burden itself and does so — result count, ordering, and fields returned are all stated. Together with the sibling routing, an agent has everything needed to call it correctly on the first attempt.

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, and the description earns an extra point by explaining that all filters are optional and combine freely and by restating the limit's no-pagination implication. It does not add format detail for city or date fields beyond what the schema already supplies.

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 (search FrontRowTickets.com ticket inventory) and enumerates the filter dimensions (free text, city, date range, category). It also positions itself as the entry point ('Start here for discovery'), which distinguishes it from the more targeted siblings.

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?

Explicitly gives the default entry point plus two routing rules: use get_event for one event's full record, and get_deals when the user has a hard budget cap. That is real when-to-use guidance with named alternatives, not an implied preference.

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 toolsInspect
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