Skip to main content
Glama

Seats and prices for one day

get_event
Read-only

Every way to buy seats for one day and court: the seats (gangway, row, seat once assigned), price per ticket and total, cheapest first, and the buy_url that opens the day on the site with the party size selected.

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_slug": "<event_slug>"
    },
    "name": "get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityNoSeats wanted together (1 to 4).
event_slugYesFrom search_events, or the last part of the day's URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral facts: results are ordered cheapest first, seat identifiers may be unassigned ('seat once assigned'), and buy_url is an external link that pre-selects the party size rather than completing a purchase. It does not state what happens when a day has no availability.

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?

One sentence, front-loaded with the core offer, then a parenthetical breakdown of returned fields. It is dense but every clause carries information; the nested parentheses around gangway/row/seat make it slightly harder to scan.

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 compensates by enumerating the returned fields and their ordering. Combined with full schema coverage on the two parameters and annotations covering the read-only profile, an agent has everything needed to call and interpret this tool.

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. The description earns above baseline by tying quantity to the output: the returned buy_url opens the site with that party size already selected, which is a consequence the schema alone does not convey. The 'day and court' phrasing also clarifies what event_slug resolves to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and return content: seat options (gangway, row, seat), per-ticket and total price, sorted cheapest first, plus a buy_url. An agent knows exactly what comes back. It does not, however, contrast itself with siblings like buying_info or search_events, so the differentiation work is left to the caller.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: this is a per-day detail lookup, so it follows an event discovery step. The upstream dependency (event_slug from search_events) appears in the schema, not the description, and there is no statement about when to prefer buying_info instead. Adequate but with clear gaps.

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