FrontRowTickets.com MCP Server

get_deals

Read-onlyIdempotent

Use when budget is the primary filter: returns the cheapest available events under a required max_price cap (applied to each event's starting price), cheapest first, up to 25 results; events without pricing data are excluded. City and date range are optional additional filters. Use search_events for text- or category-driven discovery instead.

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": {
      "max_price": "<max_price>"
    },
    "name": "get_deals"
  }
}

Input Schema

Name	Required	Description
`city`	No	City name, e.g. Chicago
`date_to`	No	Latest event date (ISO)
`date_from`	No	Earliest event date (ISO)
`max_price`	Yes	Required. Maximum starting price in USD — events above this are excluded

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026
- 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"
```

Changed1 schema field changedOct 19, 2026

changedInput schema / properties / max_price / description

Previous value: -"Maximum starting price in USD"New value: +"Required. Maximum starting price in USD — events above this are excluded"

First observedOct 19, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing result ordering (cheapest first), a result ceiling (up to 25), the exclusion rule (events without pricing data are dropped), and the precise scope of the cap (applied per event to its starting price). These are exactly the behaviors that change how an agent interprets an empty or short result set.

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?

Two sentences, front-loaded with the usage trigger and the cap semantics before the optional filters and the routing pointer. No redundant restatement of the tool name or title.

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?

For a filter-driven read tool with no output schema, the description covers the input contract, ordering, result cap, and exclusion behavior. What is returned per event is not described, but that is a minor gap given the absence of an output schema and the low risk of misuse.

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 interpretive value: it clarifies that max_price is a per-event cap on starting price rather than a total-budget figure, and that city/date range act only as narrowing filters on the deal search. It does not add format detail for the date parameters, which the schema already covers.

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 ('returns the cheapest available events') plus the governing constraint (required max_price cap). It also explicitly distinguishes itself from search_events, so an agent can pick between the two without opening a 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?

Opens with the selection condition ('Use when budget is the primary filter') and names the alternative tool and its role ('Use search_events for text- or category-driven discovery instead'). Both the when and the when-not are explicit.

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?