livetennisapi-mcp

Head-to-head

get_h2h

Read-onlyIdempotent

The all-time record between two players, across BOTH halves of the product. That is the results archive (1968 to 2022) plus the completed matches from 2023 onward. Names are the keys. An ambiguous fragment returns the candidate list to choose from, and nothing is guessed. Totals count only meetings with a known winner. Walkovers and retirements are part of the record, and each meeting carries its outcome. Requires the BASIC plan or any History plan.

Input Schema

Name	Required	Description	Default
`player1`	Yes	First player name (fragment, min 3 chars), e.g. "federer".
`player2`	Yes	Second player name (fragment, min 3 chars), e.g. "nadal".

Output Schema

Name	Required	Description
`ok`	Yes	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.
`totals`	No	The headline record.
`message`	Yes	Human-readable summary of the result, safe to relay to the user verbatim.
`players`	No	The resolved names. Null when no player matches the fragments.
`meetings`	No	Individual meetings, newest first, capped at 200.
`by_surface`	No	Decided wins per surface. The keys are surface names plus "unknown".

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 28, 2026

changedOutput schema / properties / by_surface / description

Previous value: -"Decided wins per surface; keys are surface names plus \"unknown\"."New value: +"Decided wins per surface. The keys are surface names plus \"unknown\"."

changedOutput schema / properties / meetings / items / properties / era / description

Previous value: -"\"archive\" (results archive, 1968-2022) or \"current\" (our own completed matches, 2023 onward)."New value: +"\"archive\" (results archive, 1968-2022) or \"current\" (completed matches from 2023 onward)."

changedOutput schema / properties / meetings / items / properties / match_id / description

Previous value: -"Our match id (current era rows) — pass to get_match."New value: +"Our match id (current era rows). Pass to get_match."

changedOutput schema / properties / meetings / items / properties / outcome / description

Previous value: -"completed, retired, walkover, … — exclude non-completed yourself if needed."New value: +"completed, retired, walkover, ... Exclude non-completed yourself if needed."

changedOutput schema / properties / meetings / items / properties / score / description

Previous value: -"Final score (archive rows only — read current rows from get_match)."New value: +"Final score (archive rows only. Read current rows from get_match)."

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 / players / description

Previous value: -"The resolved names; null when no player matches the fragments."New value: +"The resolved names. Null when no player matches the fragments."

changedOutput schema / properties / totals / properties / undecided / description

Previous value: -"Meetings with no derivable winner — never counted in wins."New value: +"Meetings with no derivable winner. Never counted in wins."

AddedAug 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavior: it spans both data halves, does not guess on ambiguous names, counts only meetings with a known winner, includes walkovers and retirements, and carries each meeting's outcome. It also adds a plan requirement, which is useful operational context.

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?

The description is front-loaded with the core purpose and then adds relevant behavioral details. It is slightly longer than necessary, but nearly every sentence contributes useful calling context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema and full parameter descriptions, the description supplies the remaining important context: data coverage, ambiguity handling, counting rules, inclusion of walkovers/retirements, and plan requirements. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter syntax is already well documented. The description adds meaningful semantics by explaining that names are keys and that ambiguous fragments return a candidate list rather than guessing.

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?

The description states a specific resource: the all-time head-to-head record between two players. It also distinguishes the scope from archive-only tools by explicitly covering both the 1968-2022 archive and completed matches from 2023 onward.

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?

It gives clear usage context: names are the keys, ambiguous fragments return candidates, and a BASIC or History plan is required. It does not explicitly compare this tool to sibling alternatives, but the scope is specific enough that an agent can infer when to use it.

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

All livetennisapi-mcp tools Inspect

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.