Skip to main content
Glama
livetennisapi

livetennisapi-mcp

by livetennisapi
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

Upcoming matches

get_upcoming_matches
Read-onlyIdempotent

Find upcoming tennis matches with player and tournament details. Use date range, tour, player, or country filters to narrow results.

Instructions

List tennis matches scheduled to start soon, with players and tournament.

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. Dates show when Glama detected each change.

  1. 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"
+]
  2. 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"
+}
  3. First observedv1.0.4

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish the read-only, idempotent, and non-destructive nature. The description adds minimal behavioral context by specifying the matches are upcoming ('scheduled to start soon'), but does not disclose additional traits such as default time window, ordering, or dynamic nature beyond what openWorldHint already implies.

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?

The description is a single, front-loaded sentence with no redundant information. It fits the tool's simplicity and is appropriately concise.

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

Completeness3/5

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

With strong annotations and full schema coverage, the description covers the core purpose. However, it lacks usage guidance and doesn't differentiate from sibling scheduling tools, leaving an agent to infer when 'upcoming' applies as opposed to 'fixtures' or 'live' 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?

The input schema has 100% parameter descriptions, so the baseline is 3. The description does not provide additional parameter meaning; it only vaguely references 'players and tournament' which maps to the player and tour parameters.

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?

Description clearly states the tool lists tennis matches with a time scope ('scheduled to start soon') and includes players and tournament. It uses a specific verb and resource, but does not explicitly distinguish itself from sibling tools like get_live_matches or get_fixtures, so it gets a 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. Sibling tools such as get_live_matches, get_fixtures, and get_recent_results suggest overlapping functionality, but the description gives no usage context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/livetennisapi/livetennisapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server