Skip to main content
Glama

livetennisapi-mcp

by io.github.livetennisapi
OverviewDiscussionsAdmin

Results archive (1968–2022)

search_archive_matches
Read-onlyIdempotent

Search the results archive: completed-match RESULTS from 1968 through 2022. ATP and WTA, main draws, qualifying and the ITF/futures tiers. Each record has winner and loser, final score, and seeds and ranks AT THE TIME of the match. Use this for historical questions ("Borg's Wimbledon finals"). The archive ends 2022-12-31, where the current results (get_recent_results) begin. Requires the BASIC plan or any History plan.

Input Schema

NameRequiredDescriptionDefault
toNoLatest tournament START date, YYYY-MM-DD.
fromNoEarliest tournament START date, YYYY-MM-DD.
tourNoatp or wta.
levelNoTier code: G=grand slam, M=masters, A=tour, F=finals, D=davis cup, C=challenger, O=olympics. Or a futures category code (e.g. 15).
limitNoMaximum results to return (1-200).
roundNoRound code, e.g. F for finals.
player_nameNoCase-insensitive fragment of EITHER player's name, min 3 chars, e.g. "borg".

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.
resultsNoArchive results, newest tournament first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / level / description
      Previous value: -"Source tier code: G=grand slam, M=masters, A=tour, F=finals, D=davis cup, C=challenger, O=olympics, or a futures category code (e.g. 15)."New value: +"Tier code: G=grand slam, M=masters, A=tour, F=finals, D=davis cup, C=challenger, O=olympics. Or a futures category code (e.g. 15)."
    • 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 / results / items / properties / event_date / description
      Previous value: -"The tournament START date — per-match dates do not exist in this era’s records."New value: +"The tournament START date. Per-match dates do not exist in this era's records."
    • changedOutput schema / properties / results / items / properties / level / description
      Previous value: -"Source tier code: G, M, A, F, D, C, O, or a futures category code."New value: +"Tier code: G, M, A, F, D, C, O, or a futures category code."
    • changedOutput schema / properties / results / items / properties / outcome / description
      Previous value: -"completed, retired, walkover, default or abandoned — parsed, null when unparseable."New value: +"completed, retired, walkover, default or abandoned. Parsed, null when unparseable."
    • changedOutput schema / properties / results / items / properties / tour / description
      Previous value: -"atp or wta — the results archive covers those two tours."New value: +"atp or wta. The results archive covers those two tours."
    • changedOutput schema / properties / results / items / properties / winner / description
      Previous value: -"The winner — a stored field in the corpus, never an inference."New value: +"The winner, a stored field in the corpus, never an inference."
    • changedOutput schema / properties / results / items / properties / winner / properties / entry / description
      Previous value: -"Draw entry where recorded (WC, Q, LL, …) — null for direct acceptances."New value: +"Draw entry where recorded (WC, Q, LL, ...). Null for direct acceptances."
    • changedOutput schema / properties / results / items / properties / winner / properties / player_id / description
      Previous value: -"Corpus person id — pass to search_archive_players results to join bios. NOT a roster player id."New value: +"Corpus person id. Join it to search_archive_players results for bios. NOT a roster player id."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description only needs supplementary context — it adds the plan/entitlement requirement and the hard archive cutoff. It does not discuss rate limits or result ordering, keeping it just under a 5.

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?

Front-loaded with the core verb and scope, and the boundary with the sibling tool comes before the plan note. Dense but nearly every clause carries information; slightly longer than strictly needed.

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?

Output schema and annotations already cover return shape and safety, and the description fills in scope, tiers, and the archive cutoff. Only minor gaps remain (ordering, pagination behavior beyond the limit parameter).

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 each parameter has an inline description, so the schema carries the semantics; the description adds only the 'seeds and ranks at the time' interpretation of returned fields rather than parameter guidance. Baseline 3 is appropriate.

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

Purpose5/5

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

Specific verb plus resource with explicit scope ('completed-match RESULTS from 1968 through 2022'), tours and tiers covered, and what each record contains. It is clearly distinguishable from get_recent_results by the stated 2022-12-31 archive boundary.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger (historical questions like "Borg's Wimbledon finals") and names the alternative, get_recent_results, along with the date boundary that separates them. It also states the subscription prerequisite.

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