livetennisapi-mcp

Archive player bios

search_archive_players

Read-onlyIdempotent

The people of the results archive (1968 to 2022): hand, date of birth, country, height, and career-high rank with the week it was first reached. Their ids are corpus person ids (the winner/loser player_id on archive results), not roster ids. For current players use search_players. Requires the BASIC plan or any History plan.

Input Schema

Name	Required	Description
`tour`	No	atp or wta.
`limit`	No	Maximum players to return (1-200).
`query`	Yes	Full or partial player name, min 3 chars, e.g. "navratilova".

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.
`message`	Yes	Human-readable summary of the result, safe to relay to the user verbatim.
`players`	No	Matching archive people, ordered by name.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 28, 2026

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 / items / properties / career_high_rank / description

Previous value: -"Career-high rank, from the corpus’s own weekly tables."New value: +"Career-high rank, from the archive's weekly ranking tables."

changedOutput schema / properties / players / items / properties / id / description

Previous value: -"Corpus person id — the id archive match rows carry as winner/loser player_id. NOT a roster id."New value: +"Corpus person id, the id archive match rows carry as winner/loser player_id. NOT a roster id."

AddedAug 13, 2026

TDQS

A4.4/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 goes further with two things structured data does not carry: the plan requirement and the crucial id-space warning that ids are corpus person ids (winner/loser player_id on archive results), not roster ids. Return-shape detail is deferred to the output schema, which is appropriate.

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?

Three tight sentences ordered as scope → id semantics → alternative routing, which is the right priority. Minor deductions for the awkward opening 'The people of the results archive' and the ambiguous bare token 'hand' instead of 'handedness'.

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?

An output schema exists to explain returns, all three params are schema-documented, and the description still covers the things schema and annotations cannot: plan entitlement and id provenance. Nothing needed to select or invoke the tool correctly is missing.

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%, with query (min 3 chars, example), tour enum, and limit bounds all documented in the schema. The description adds no syntax or semantics beyond that, so it lands at the baseline for fully-covered schemas.

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?

States a specific verb and resource (search the results archive for player bios) with an explicit scope of 1968–2022 and the fields returned (hand, DOB, country, height, career-high rank). It is unambiguously distinguishable from search_players, which it names.

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?

Explicitly routes the agent: 'For current players use search_players,' isolating this tool to historical/archive lookups. It also states the entitlement condition (BASIC plan or any History plan), which is a genuine gate on when the call will succeed.

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.