Retrieves only recent timeline events for a live match (used for live updates). [CRITICAL]: Requires a valid matchId obtained from getEvents or getLiveEvents.
| Name | Required | Description | Default |
|---|---|---|---|
| matchId | Yes | The unique numeric ID. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the key behavioral trait of returning only recent events for live matches, and emphasizes the critical need for a valid matchId from specific sources. However, it does not describe what 'recent' means, the exact output format, or behavior for non-live matches.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long, with the purpose front-loaded. The critical note is placed at the end using [CRITICAL] to draw attention. Every sentence earns its place with no redundant content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given that the tool has only one parameter, no output schema, and no annotations, the description sufficiently covers the purpose, the main prerequisite, and the use case for live updates. It does not fully explain return value structure or edge cases, but this is a simple retrieval tool and the description is adequate for an agent to select and invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a single parameter 'matchId' described as 'The unique numeric ID.' The description adds value by clarifying that this ID must be obtained from getEvents or getLiveEvents, providing source context beyond the schema's generic description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool 'Retrieves only recent timeline events for a live match', specifying the verb, resource, and scope. It distinguishes from the sibling tool 'get_match_timeline' by emphasizing 'only recent' and 'for a live match'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'used for live updates' provides explicit context for when to use the tool. It further gives a prerequisite: 'Requires a valid matchId obtained from getEvents or getLiveEvents', indicating a dependency. However, it does not explicitly mention when not to use it or name alternative tools for non-live scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes (e.g., timelines vs stats vs lineups), but there are several closely related match-stat and season-fixture tools that could be confused, such as get_match_stats vs get_detailed_match_stats vs get_match_details_extended.
All tools use a consistent get_ prefix and snake_case, but naming conventions vary in structure (e.g., get_season_fixtures2 vs get_livescore_season_fixtures) and one tool includes an arbitrary number suffix ('fixtures2'), which is a minor deviation.
With 41 tools, the server is significantly overscoped for typical MCP use. Although the soccer domain is broad, the sheer number of highly granular tools makes it heavy and harder to navigate.
The tool set covers nearly every aspect of soccer data: fixtures, live scores, match details, standings, top scorers, injuries, referees, team streaks, and more. Minor gaps exist, such as no direct team search or player match performance, but the surface is otherwise comprehensive.