Skip to main content
Glama

livetennisapi-mcp

by io.github.livetennisapi
OverviewDiscussionsAdmin

Tournament catalogue

search_tournaments
Read-onlyIdempotent

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).

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. Changed6 schema fields changed
    • 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. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the useful access-tier fact (free plan, no card), but says nothing about result ordering, rate limits, or behavior when query matches nothing. It also lists return fields, which the output schema already carries.

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 verb+resource and the id linkage immediately after. The return-field sentence is partially redundant with the output schema, and "where curated" is vague, but nothing is padded.

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?

With an output schema present, the return-value burden is lifted and the annotations cover safety. The description still conveys scope, empty-query behavior, the id handoff to match objects, and plan eligibility. Only result ordering and match semantics remain unstated, which are minor for a free-text 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 description coverage is 100%, including the tour enum and the limit bound of 1-200, so the description need not restate parameter mechanics. It adds no semantics beyond the schema — no guidance on matching behavior (case sensitivity, partial word matching) for query, which is the one thing the schema does not say.

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?

"Search the tournament catalogue" is a specific verb+resource, and the note that its ids are the tournament_id carried by match objects makes the catalogue's role in the data model concrete. It stops short of naming get_tournament as the follow-up sibling, so differentiation from that lookup tool is implied rather than stated.

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?

The description gives concrete invocation guidance: "Omit to list all" for the query parameter and the note that the tool works on the FREE plan with no card. It lacks an explicit when-not clause or a pointer to get_tournament for single-record lookup, leaving the sibling boundary to inference.

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

All livetennisapi-mcp toolsInspect
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