Skip to main content
Glama

Search Wimbledon days and tickets

search_events
Read-only

Find days of The Championships, Wimbledon with Debenture tickets for sale, with the cheapest price for the party size. Each day is listed per show court (Centre Court or No. 1 Court). Prices are per ticket in GBP and are what the buyer pays: there is no buyer fee. Returns a buy_url per day: give it to the person, who signs in and pays on the site.

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
courtNoShow court.
roundNoWords to match in the day's name, e.g. "final", "quarter", "2nd round", "doubles".
to_dateNoLatest day, YYYY-MM-DD.
quantityNoSeats wanted together (1 to 4).
from_dateNoEarliest day, YYYY-MM-DD.
include_sold_outNoAlso list upcoming days with nothing for sale.
max_price_per_ticketNoUpper limit per ticket, GBP.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description does add real behavioral context beyond that: prices are per ticket in GBP, there is no buyer fee, each day is broken out per show court, and a buy_url is returned for the person to complete payment off-tool. It says nothing about result limits, ordering, or what an empty result looks like, so it stops short of full transparency.

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?

Three sentences, front-loaded with what is returned before the operational note about buy_url. Every sentence carries information, though the final clause about signing in and paying is phrased awkwardly ('give it to the person, who signs in'). No filler or repetition of the 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 seven-parameter, zero-required search with no output schema, the description covers the commercially important facts: currency, no buyer fee, per-court granularity, and the buy_url handoff, which substitutes for a missing output schema. What remains unstated — result ordering, caps on result count, and behaviour when nothing matches — is minor but not negligible.

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?

Schema description coverage is 100%, so every parameter is already documented in structured form and the baseline is 3. The description adds only marginal meaning: the 'cheapest price for the party size' phrasing hints that quantity affects price selection, and 'listed per show court' loosely corresponds to the court enum, but round, date bounds, include_sold_out, and max_price_per_ticket get no extra explanation.

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?

Names a specific verb and resource ('Find days of The Championships, Wimbledon with Debenture tickets for sale') and pins down the unit of return (one entry per day, per show court). It never references the siblings buying_info or get_event, so an agent must infer the boundary itself, which keeps it short of a 5.

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: 'give it to the person, who signs in and pays on the site' tells the agent what to do with the result, and the ticket-for-sale framing implies when to call it. There is no explicit when-not condition and no routing to buying_info or get_event for adjacent information needs.

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