Skip to main content
Glama

livetennisapi-mcp

by io.github.livetennisapi
OverviewDiscussionsAdmin

Match statistics

get_match_statistics
Read-onlyIdempotent

In-play (or final) statistics for one match, in TWO families kept separate on purpose. DERIVED is rebuilt from the point-by-point record (holds/breaks, break points, service/return points). MEASURED is counted per match. It includes what no point record can yield: aces, double faults, the serve split, winners/unforced errors. Measured coverage varies by tour. Absent fields are omitted, never zero-filled. Requires the ULTRA plan.

Input Schema

NameRequiredDescriptionDefault
match_idYesMatch id, as returned by get_live_matches, get_upcoming_matches or get_recent_results.

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.
statisticsNoThe statistics.

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 / statistics / properties / coverage / description
      Previous value: -"live | final | stale | none | diverged — summarises the response."New value: +"live | final | stale | none | diverged. Summarises the response."
    • changedOutput schema / properties / statistics / properties / freshness / description
      Previous value: -"Per-family coverage/as_of/age. The two ages use DIFFERENT clocks (derived: against the newest score row; measured: wall clock) and must not be compared. On diverged the measured values are withheld and measured_divergence says why."New value: +"Per-family coverage/as_of/age. The two ages use DIFFERENT clocks (derived: against the newest score row, measured: wall clock) and must not be compared. On diverged the measured values are withheld and measured_divergence says why."
    • changedOutput schema / properties / statistics / properties / players / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "p1": {
-        "anyOf": [
-          {
-            "additionalProperties": false,
-            "properties": {
-              "derived": {
-                "additionalProperties": {
-                  "type": [
-                    "number",
-                    "null"
-                  ]
-                },
-                "description": "Rebuilt from the point-by-point record: service/return games and points, hold_pct, break_pct, break points faced/saved/converted. Null percentages mean a zero denominator, never 0.",
-                "type": "object"
-              },
-              "measured": {
-                "anyOf": [
-                  {
-                    "additionalProperties": {
-                      "type": [
-                        "number",
-                        "null"
-                      ]
-                    },
-                    "type": "object"
-                  },
-                  {
-                    "type": "null"
-                  }
-                ],
-                "description": "Counted upstream — aces, double_faults, the serve split, winners/unforced errors where covered. Absent fields are omitted, never zero-filled. Quantities named in both families are computed two different ways: a cross-check, not a duplication."
-              }
-            },
-            "required": [
-              "derived",
-              "measured"
-            ],
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "p2": {
-        "anyOf": [
-          {
-            "$ref": "#/properties/statistics/properties/players/anyOf/0/properties/p1/anyOf/0"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "p1",
-      "p2"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "p1": {
+        "anyOf": [
+          {
+            "additionalProperties": false,
+            "properties": {
+              "derived": {
+                "additionalProperties": {
+                  "type": [
+                    "number",
+                    "null"
+                  ]
+                },
+                "description": "Rebuilt from the point-by-point record: service/return games and points, hold_pct, break_pct, break points faced/saved/converted. Null percentages mean a zero denominator, never 0.",
+                "type": "object"
+              },
+              "measured": {
+                "anyOf": [
+                  {
+                    "additionalProperties": {
+                      "type": [
+                        "number",
+                        "null"
+                      ]
+                    },
+                    "type": "object"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Counted per match: aces, double_faults, the serve split, winners/unforced errors where covered. Absent fields are omitted, never zero-filled. Quantities named in both families are computed two different ways: a cross-check, not a duplication."
+              }
+            },
+            "required": [
+              "derived",
+              "measured"
+            ],
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "p2": {
+        "anyOf": [
+          {
+            "$ref": "#/properties/statistics/properties/players/anyOf/0/properties/p1/anyOf/0"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "p1",
+      "p2"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / statistics / properties / players / description
      Previous value: -"Null when coverage is none — the match exists and holding nothing is the honest answer."New value: +"Null when coverage is none. The match exists, and holding nothing is the honest answer."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world profile, so the bar is lower. The description adds genuinely useful behavioral context beyond them: the ULTRA plan requirement, tour-dependent coverage of measured stats, and the non-zero-filling omission policy.

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-loads the core claim (in-play or final statistics for one match) and then explains the derived/measured split efficiently. Slightly dense, but every sentence carries information about scope, coverage, or requirements.

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-value details need not be restated, and annotations cover the safety profile. The description fills the remaining gaps an agent needs: the two-family structure, omitted-vs-zero semantics, variable coverage, and the plan prerequisite.

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?

There is only one parameter, and the schema documents match_id at 100% coverage, including where to obtain it from live, upcoming, or recent results tools. The description adds no parameter-specific semantics beyond that baseline.

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 and resource: statistics for one match, split into DERIVED and MEASURED families, with examples of the metrics in each. It is clear what the tool returns, but it does not explicitly differentiate itself from nearby siblings like get_match_analysis or get_match_score.

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?

Implies usage by saying it covers in-play or final statistics for a single match, which signals when it applies. However, it offers no explicit when-not guidance or alternatives, so the agent must infer whether get_match_analysis or get_match_score is more appropriate for a given need.

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