Skip to main content
Glama
livetennisapi-mcp

livetennisapi-mcp

Fixture schedule

get_fixtures
Read-onlyIdempotent

Retrieves upcoming tennis fixtures in chronological order, filterable by tour, so you can see what matches are scheduled this week.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fixtures"
  }
}

Input Schema

NameRequiredDescriptionDefault
tourNoTour filter. Each name covers its doubles variants. Exhibition/team events carry no tour and are excluded whenever the filter is used.
limitNoMaximum fixtures to return (1-200).

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.
fixturesNoScheduled fixtures, earliest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.6.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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."
  2. Changed1 schema field changedv1.4.0
    • 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"
      +}
  3. Changed2 schema fields changedv1.2.0
    • addedInput schema / properties / limit / description
      Added value: +"Maximum fixtures to return (1-200)."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "fixtures": {
      +      "description": "Scheduled fixtures, earliest first.",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "event_date": {
      +            "description": "Scheduled start, ISO timestamp.",
      +            "type": [
      +              "string",
      +              "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.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "tournament": {
      +            "description": "Event name.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "event_date",
      +          "tournament",
      +          "round",
      +          "player1",
      +          "player2"
      +        ],
      +        "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

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive. The description adds real behavioral context beyond them: results are ordered earliest-first, the list is filterable by tour, and the endpoint is usable on the free plan with no card. It does not mention pagination or result size limits, which the schema partially covers via 'limit'.

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, front-loaded with the resource and ordering, then usage, then plan availability. Nothing is redundant or padded.

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 and full parameter documentation, the description needs only purpose, ordering and access notes, all of which it supplies. The remaining gap is disambiguation from the very similar get_upcoming_matches sibling.

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%, so the tour enum mechanics (doubles variants, exclusion of exhibition/team events) are already fully documented in the schema. The description only restates that the schedule is 'filterable by tour' and adds no format or semantic detail beyond that.

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+resource ('Upcoming scheduled tennis fixtures') and adds a scope qualifier that distinguishes a forward-looking schedule. However, it never differentiates itself from the sibling get_upcoming_matches, which an agent would reasonably read as the same thing.

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?

The line 'Use this for "what is on this week"' gives an implied usage scenario, but there is no explicit when-not-to-use and no mention of get_upcoming_matches or get_live_matches as alternatives, leaving the agent to guess between near-duplicate siblings.

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