livetennisapi-mcp

Fixture schedule

get_fixtures

Read-onlyIdempotent

Upcoming scheduled tennis fixtures, earliest first. This is the forward schedule, filterable by tour. Use this for "what is on this week". Works on the FREE plan (no card needed).

Input Schema

Name	Required	Description	Default
`tour`	No	Tour filter. Each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used.
`limit`	No	Maximum fixtures to return (1-200).

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.
`fixtures`	No	Scheduled fixtures, earliest first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

changedInput schema / properties / tour / description

Previous value: -"Tour filter; each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used."New value: +"Tour filter. Each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used."

changedOutput schema / properties / fixtures / items / properties / event_date / description

Previous value: -"Scheduled start, ISO timestamp."New value: +"Scheduled date, YYYY-MM-DD."

addedOutput schema / properties / fixtures / items / properties / start_time

Added value: +{
+  "description": "Scheduled start, UTC ISO-8601. Null until the order of play assigns a time.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

changedOutput schema / properties / fixtures / items / required

Previous value: -[
-  "event_date",
-  "tournament",
-  "round",
-  "player1",
-  "player2"
-]New value: +[
+  "event_date",
+  "start_time",
+  "tournament",
+  "round",
+  "player1",
+  "player2"
+]

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

Changed1 schema field changedAug 13, 2026

addedInput schema / properties / tour

Added value: +{
+  "description": "Tour filter; each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used.",
+  "enum": [
+    "atp",
+    "wta",
+    "challenger",
+    "itf",
+    "juniors"
+  ],
+  "type": "string"
+}

First observedJul 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is covered. The description earns credit by adding traits annotations cannot express: the guaranteed sort order (earliest first), the forward-looking window, and that it works on the free plan with no card required.

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 short sentences, front-loaded with the resource and its ordering, followed by the use case and the access constraint. 'This is the forward schedule' mildly repeats 'Upcoming scheduled', but nothing else is wasted.

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, return values need no explanation, and both parameters are fully documented. The description covers ordering, filtering intent and plan access. The only real gap is the unstated boundary against get_upcoming_matches.

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 tour parameter's enum plus its doubles/exhibition caveat is fully documented in the schema itself. The description only restates 'filterable by tour' and adds nothing on limit or ordering interaction, so baseline 3 applies.

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 resource and scope: upcoming scheduled tennis fixtures, returned earliest first, filterable by tour. That is much more than a restatement of the name. However, it never distinguishes itself from the sibling get_upcoming_matches, which an agent must otherwise infer from the 'fixtures' vs 'matches' wording.

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?

Gives a concrete selection scenario — 'what is on this week' — which tells the agent when this tool fits. It stops short of exclusions or naming the alternative to use for historical or live data, so the agent gets context but not routing.

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.