Skip to main content
Glama

NeedATicket ticket prices

Get one event's prices by section and over time

get_event_prices
Read-onlyIdempotent

Prices for one event found with search_ticket_prices: its current "from" price, the cheapest price in each seating section, the daily lowest price over the last 30 days, whether it is rising or falling against a week ago, how many listings there are, and the link for a free price-drop alert. Pass the eventId from a search_ticket_prices result. Use it for questions like "which section is cheapest?", "has the price gone up?" or "is now a good time to buy?". Prices are per ticket before the seller's fees, from StubHub listings checked by NeedATicket.co.uk.

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

Input Schema

NameRequiredDescriptionDefault
event_idYesThe eventId of a search_ticket_prices result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered; the description adds genuinely new behavioral context beyond that: prices are per ticket before seller fees, sourced from StubHub listings checked by NeedATicket.co.uk, and the trend is computed over a 30-day window against one week ago. It does not discuss freshness/caching or data gaps for events with sparse listings, which keeps it off a 5.

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 source tool are front-loaded, and the returned data is enumerated in a single readable sequence followed by example use cases. The middle enumeration is dense (one long comma-chained sentence) but every element listed is information the agent needs because there is no output schema.

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?

No output schema exists, so the description carries the full burden of describing return values and does so item by item, including units (per ticket, before fees), provenance, and the time horizon of the trend. Combined with a single fully documented required parameter and complete annotations, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only one parameter at 100% schema coverage, the schema already documents event_id, its pattern, and its origin. The description's 'Pass the eventId from a search_ticket_prices result' echoes that provenance rather than adding new format or validation meaning, so the baseline 3 applies.

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 and resource ('Prices for one event') and enumerates exactly what is returned: current from-price, cheapest per section, 30-day daily low, trend vs. a week ago, listing count, and alert link. It also names its sibling search_ticket_prices as the source of the eventId, so the agent can distinguish 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear prerequisite ('Pass the eventId from a search_ticket_prices result') and three concrete question shapes that select this tool ('which section is cheapest?', 'has the price gone up?', 'is now a good time to buy?'). It stops short of an explicit negative rule or a statement of when to prefer search_ticket_prices instead, so it is strong context but not full routing.

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