Skip to main content
Glama
livetennisapi-mcp

livetennisapi-mcp

Tournament catalogue

search_tournaments
Read-onlyIdempotent

Find tennis tournaments by name or tour, returning IDs plus surface, indoor, host city/country, and category for match lookups.

Instructions

Search the tournament catalogue. Its ids are the tournament_id that match objects carry. Returns surface, indoor, host city/country and category where curated. Works on the FREE plan (no card needed).

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

Input Schema

NameRequiredDescriptionDefault
tourNoRestrict to one tour.
limitNoMaximum tournaments to return (1-200).
queryNoFull or partial tournament name, e.g. "wimbledon". Omit to list all.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the request succeeded, including when the answer is an empty list. False for a missing or rejected key, a plan that does not include this data, an unknown id, a rate limit or a network error. The message then says what to do. check_api_status is the exception: it is true whenever the API answered, and reports API key problems in the message.
messageYesHuman-readable summary of the result, safe to relay to the user verbatim.
tournamentsNoMatching tournaments, name order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.6.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / properties / message / description
      Previous value: -"Human-readable summary. Identical to the text content, so either half can be used alone."New value: +"Human-readable summary of the result, safe to relay to the user verbatim."
    • changedOutput schema / properties / ok / description
      Previous value: -"True when the call returned data. False for a tier wall, a missing or rejected key, or an empty result — all of which are normal states with a clear remedy, not failures."New value: +"True when the request succeeded, including when the answer is an empty list. False for a missing or rejected key, a plan that does not include this data, an unknown id, a rate limit or a network error. The message then says what to do. check_api_status is the exception: it is true whenever the API answered, and reports API key problems in the message."
    • changedOutput schema / properties / tournaments / items / properties / category / description
      Previous value: -"Tournament category (grand_slam, masters_1000, tour_finals, atp_500, atp_250, wta_1000, wta_500, wta_250, wta_125, challenger, itf, juniors). Set only where the catalogues agree unambiguously — null otherwise, never derived from the name."New value: +"Tournament category (grand_slam, masters_1000, tour_finals, atp_500, atp_250, wta_1000, wta_500, wta_250, wta_125, challenger, itf, juniors). Set only where the category is unambiguous. Null otherwise, never derived from the name."
    • changedOutput schema / properties / tournaments / items / properties / city / description
      Previous value: -"Host city, from a curated table — null where not curated."New value: +"Host city, from a curated table. Null where not curated."
    • changedOutput schema / properties / tournaments / items / properties / country / description
      Previous value: -"Host country, ISO-3166 alpha-2 — null where not curated."New value: +"Host country, ISO-3166 alpha-2. Null where not curated."
    • changedOutput schema / properties / tournaments / items / properties / id / description
      Previous value: -"Stable tournament id — the same id match objects carry as tournament_id."New value: +"Stable tournament id, the same id match objects carry as tournament_id."
  2. Addedv1.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real context beyond them: the result fields (surface, indoor, host city/country, category where curated), the caveat that category is only populated when curated, and the free-plan/no-card constraint. That is useful behavioral disclosure, though pagination/limit behavior and the total-count semantics are left to the schema.

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?

Four short sentences, front-loaded with the core action, then id linkage, then return shape, then the plan constraint. Each sentence carries distinct information with no repetition. Slightly fragmented prose, but nothing is wasted.

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?

An output schema exists, so return values are largely covered, and the description still summarizes the key fields. All three parameters are documented in the schema. The remaining gap is sibling differentiation against get_tournament and any note on result ordering or how search matches names — minor for a simple catalogue search.

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 coverage is 100% — query, tour enum, and limit are all documented inline with examples and bounds. The description adds nothing about parameter semantics, so this sits at the baseline 3 where the schema does all the work.

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?

The description gives a specific verb and resource ("Search the tournament catalogue") and clarifies the identifier contract — returned ids are the tournament_id that match objects carry — which is genuinely distinguishing information. It does not explicitly contrast with the sibling get_tournament, so an agent must infer that this is the lookup/list tool and that one is the single-fetch tool.

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 implied rather than stated: search to find a tournament, then presumably use its id elsewhere. There is no explicit when-to-use/when-not, and no mention of get_tournament as the alternative for fetching a known tournament by id. The free-plan note helps an agent decide it can call this cheaply, but that is a constraint, not routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.