Skip to main content
Glama
livetennisapi-mcp

livetennisapi-mcp

Match timeline

get_match_events
Read-onlyIdempotent

Retrieve a match's event timeline with breaks, games won, sets won and momentum runs to track how the scoreline developed, using a match id from live, upcoming or recent results.

Instructions

Timeline of events for a match: breaks, games won, sets won, momentum runs. Requires the PRO plan.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "match_id": "<match_id>"
    },
    "name": "get_match_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum events to return (1-200).
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.
eventsNoEvents, newest first, as the API returns them.
messageYesHuman-readable summary of the result, safe to relay to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.6.5
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / match_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / match_id / minimum
      Added value: +-9007199254740991
    • changedOutput schema / properties / events / description
      Previous value: -"Events in chronological order."New value: +"Events, newest first, as the API returns them."
    • 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. Addedv1.3.0
  3. Removedv1.2.1
  4. Addedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the PRO plan requirement, which is genuine context beyond annotations, but says nothing about event ordering, truncation behavior when limit is hit, or response shape.

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?

Two short sentences with zero filler; the payload (what the timeline contains) is front-loaded and the prerequisite follows. Nothing could be removed without losing information.

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 only two well-documented parameters and an output schema present, the description needn't explain return values. What it lacks is minor: whether events come back in chronological order and whether limit truncates the timeline.

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%, with limit (1-200, default 30) and match_id both documented in the schema, including cross-references to how to obtain a match_id. The description adds no parameter meaning beyond that, so the 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 enumerates the event types returned (breaks, games won, sets won, momentum runs), which separates it from sibling stat tools like get_match_score and get_match_statistics. It does not explicitly name a sibling, so it stops short of a 5.

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 PRO plan prerequisite is stated, which is useful gating context, but there is no guidance on when to choose this over get_match_statistics, get_match_analysis, or get_match_score. Usage is only implied by the event-type list.

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