Skip to main content
Glama

livetennisapi-mcp

by io.github.livetennisapi
OverviewDiscussionsAdmin

Tournament detail

get_tournament
Read-onlyIdempotent

One tournament by its stable id, the tournament_id carried on match objects. Name, tour, surface, indoor, plus host city/country and category where curated. Works on the FREE plan (no card needed).

Input Schema

NameRequiredDescriptionDefault
tournament_idYesStable tournament id, as returned by search_tournaments or carried on a match as tournament_id.

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.
tournamentNoThe tournament.

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 / tournament / 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 / tournament / 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 / tournament / 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 / tournament / 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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: the FREE-plan/no-card constraint and the 'where curated' qualifier warning that host city/country/category may be absent. It does not discuss error behavior for a bad id.

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?

Two compact sentences, front-loaded with the resource and identifier, then the payload, then pricing. No filler; 'where curated' is the only slightly vague phrase.

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 shape needn't be explained, yet the description still previews key fields. For a single-read lookup with full schema coverage and rich annotations, an agent has everything needed to invoke it correctly; only malformed-id behavior is unaddressed.

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% and the single parameter is fully documented in the schema, so the baseline is 3. The description reinforces provenance (stable id, carried on match objects) but adds no format or validation detail beyond the schema.

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 verb+resource (fetch one tournament by stable id) and enumerates the returned fields (name, tour, surface, indoor, host city/country, category), which tells an agent exactly what this is versus the search_tournaments sibling. It stops short of naming the sibling explicitly.

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?

Gives a practical sourcing hint — the id is 'the tournament_id carried on match objects' — which implies the workflow of going through matches, and mentions the FREE plan so the agent knows no paid tier is required. No explicit when-not or named alternative, so usage is implied rather than prescribed.

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