Skip to main content
Glama
livetennisapi

livetennisapi-mcp

by livetennisapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Upcoming matches

get_upcoming_matches
Read-onlyIdempotent

List tennis matches scheduled to start soon with players, tournament, and start time to identify who plays next or retrieve a match ID before play begins.

Instructions

List tennis matches scheduled to start soon, with players, tournament and start time. Use this for "who plays next" or to find a match id before it starts. Works on the FREE plan (no card needed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest play date: YYYY-MM-DD or ISO-8601; must not precede from.
fromNoEarliest play date: YYYY-MM-DD (a whole UTC day) or ISO-8601 datetime.
tourNoTour filter; each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used.
limitNoMaximum matches to return (1-200).
playerNoPlayer ids (from search_players), max 50 — keeps matches where ANY listed player is either participant.
countryNoEither participant's country — the lowercase 3-letter IOC-style code the Player object returns (e.g. ned, sui, gre), NOT ISO-3166. Players with no recorded country never match.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue 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.
matchesNoMatches due to start, soonest first.
messageYesHuman-readable summary. Identical to the text content, so either half can be used alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.5.0
    • addedOutput schema / properties / matches / items / properties / event_status_updated_at
      Added value: +{
+  "description": "The instant the current event_status was recorded, UTC ISO-8601 (added 2026-08-19). Null while the status has never changed since the field was introduced — never backfilled.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / matches / items / properties / has_analysis
      Added value: +{
+  "description": "Whether a model thesis or profile exists for this match (added 2026-09-02, every tier). Filter on this before calling get_match_analysis, which reports the same absence. Null only when the server predates the field.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • addedOutput schema / properties / matches / items / properties / has_market
      Added value: +{
+  "description": "Whether a match-winner market is mapped to this match (added 2026-09-02, every tier). Filter on this before calling get_match_odds, which reports the same absence. Null only when the server predates the field.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • changedOutput schema / properties / matches / items / required
      Previous value: -[
-  "id",
-  "tour",
-  "tournament",
-  "tournament_id",
-  "round",
-  "round_code",
-  "player1",
-  "player2",
-  "score",
-  "status",
-  "surface",
-  "indoor",
-  "serving",
-  "winner",
-  "event_status",
-  "withdrew",
-  "win_probability_p1"
-]New value: +[
+  "id",
+  "tour",
+  "tournament",
+  "tournament_id",
+  "round",
+  "round_code",
+  "player1",
+  "player2",
+  "score",
+  "status",
+  "surface",
+  "indoor",
+  "serving",
+  "winner",
+  "event_status",
+  "event_status_updated_at",
+  "withdrew",
+  "has_analysis",
+  "has_market",
+  "win_probability_p1"
+]
  2. Changed11 schema fields changedv1.4.0
    • addedInput schema / properties / country
      Added value: +{
+  "description": "Either participant's country — the lowercase 3-letter IOC-style code the Player object returns (e.g. ned, sui, gre), NOT ISO-3166. Players with no recorded country never match.",
+  "maxLength": 3,
+  "minLength": 3,
+  "type": "string"
+}
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Earliest play date: YYYY-MM-DD (a whole UTC day) or ISO-8601 datetime.",
+  "type": "string"
+}
    • addedInput schema / properties / player
      Added value: +{
+  "description": "Player ids (from search_players), max 50 — keeps matches where ANY listed player is either participant.",
+  "items": {
+    "type": "integer"
+  },
+  "maxItems": 50,
+  "type": "array"
+}
    • addedInput schema / properties / to
      Added value: +{
+  "description": "Latest play date: YYYY-MM-DD or ISO-8601; must not precede from.",
+  "type": "string"
+}
    • 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"
+}
    • addedOutput schema / properties / matches / items / properties / event_status
      Added value: +{
+  "description": "How the match ended (or paused) when it did not run its course: Retired, Cancelled, Walk Over, Postponed or Interrupted. Null means completed normally OR never resolved. Branch settlement logic here.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / matches / items / properties / round_code
      Added value: +{
+  "description": "Round in the normalized vocabulary (F, SF, QF, R16 … Q); null when the label is unrecognised, never guessed.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / matches / items / properties / tour
      Added value: +{
+  "description": "atp, wta, challenger, itf or juniors. Null when the feed never stated one (exhibitions, team events).",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / matches / items / properties / tournament_id
      Added value: +{
+  "description": "Stable tournament id — pass to get_tournament. Null where uncatalogued.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / matches / items / properties / withdrew
      Added value: +{
+  "description": "Completed matches only: which player retired or conceded the walkover, 1 or 2. Null means \"not a withdrawal, or no evidence\", never a guess.",
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • changedOutput schema / properties / matches / items / required
      Previous value: -[
-  "id",
-  "tournament",
-  "round",
-  "player1",
-  "player2",
-  "score",
-  "status",
-  "surface",
-  "indoor",
-  "serving",
-  "winner",
-  "win_probability_p1"
-]New value: +[
+  "id",
+  "tour",
+  "tournament",
+  "tournament_id",
+  "round",
+  "round_code",
+  "player1",
+  "player2",
+  "score",
+  "status",
+  "surface",
+  "indoor",
+  "serving",
+  "winner",
+  "event_status",
+  "withdrew",
+  "win_probability_p1"
+]
  3. Changed2 schema fields changedv1.2.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum matches to return (1-200)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "matches": {
+      "description": "Matches due to start, soonest first.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "id": {
+            "description": "Match id. Pass to get_match, get_match_score, get_match_events or get_match_odds.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "indoor": {
+            "description": "True when played indoors.",
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "player1": {
+            "description": "Name of player 1.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "player2": {
+            "description": "Name of player 2.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "round": {
+            "description": "Round within the event, e.g. \"QF\".",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "score": {
+            "description": "Formatted score line, e.g. \"6-4 3-6 2-1\".",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "serving": {
+            "description": "1 or 2 while a point is in play, otherwise null.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "status": {
+            "description": "One of live, upcoming or completed.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "surface": {
+            "description": "Court surface, e.g. hard, clay, grass.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tournament": {
+            "description": "Event name, e.g. \"Wimbledon\".",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "win_probability_p1": {
+            "description": "Model probability that player 1 wins, 0-1. Requires the ULTRA plan; null otherwise.",
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "winner": {
+            "description": "1 or 2 once decided, otherwise null.",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "id",
+          "tournament",
+          "round",
+          "player1",
+          "player2",
+          "score",
+          "status",
+          "surface",
+          "indoor",
+          "serving",
+          "winner",
+          "win_probability_p1"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "description": "Human-readable summary. Identical to the text content, so either half can be used alone.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "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.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok",
+    "message"
+  ],
+  "type": "object"
+}
  4. First observedv1.0.4

TDQS

A4/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, and idempotent behavior, so the description's burden is lighter. It adds useful context about the FREE plan eligibility and that results are 'soon'-based, but does not detail freshness, time-window defaults, or how 'soon' is bounded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with no filler: the primary behavior is front-loaded, followed by concrete use cases and a plan-eligibility note. Every sentence contributes value.

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?

For a read-only list tool with a rich output schema and fully documented parameters, the description is near-complete. It could clarify the temporal meaning of 'soon' or the relationship to get_fixtures, but the available schema and annotations cover most operational needs.

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%, so all six parameters are already documented. The description does not add parameter-level semantics beyond what the schema provides, keeping it at the baseline.

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 ('List'), a clear resource ('tennis matches scheduled to start soon'), and the included information (players, tournament, start time). The stated use cases ('who plays next', 'find a match id before it starts') also situate it relative to the broader tool family, making its purpose distinct.

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?

Explicitly says when to use this tool: for upcoming-match discovery and obtaining a match id before start. It does not name sibling alternatives or state when not to use it, so it stops short of full usage guidance.

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

Deploy Server

Other Tools