Retrieve LiveScore match statistics by providing the match URL's five-segment path; returns the stats section when the source exposes it.
LiveScore match statistics. Returns the statistics section for a LiveScore match when the source exposes it. The current Next.js build id is resolved from the public match page at request time.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Five-segment path after /en/ from a LiveScore match URL |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It does disclose two meaningful traits: statistics may not exist for every match, and the Next.js build id is resolved fresh from the public match page at request time. It stops short of describing failure modes or response behavior.
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?
Two tightly written sentences with no filler. The tool's function and the key availability caveat are front-loaded, and the build-id detail is the only secondary sentence but still earns its place.
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?
The description is adequate for a simple one-parameter fetch: it names the resource, the parameter, and a caveat. However, there is no output schema and no description of what the statistics section contains or how failures manifest when the source does not expose stats.
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%, and the schema already describes the path parameter precisely as 'Five-segment path after /en/ from a LiveScore match URL.' The description adds no additional parameter meaning beyond the structured schema, so the baseline of 3 applies.
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?
States the specific action and resource: 'Returns the statistics section for a LiveScore match.' The conditional 'when the source exposes it' adds useful scoping. It is clear but does not explicitly differentiate from related siblings like livescore_match or flashscore_match_stats.
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?
No guidance on when to prefer this tool over alternatives such as livescore_match or livescore_scores, and no when-not-to-use guidance. The only contextual hint is the conditional availability of statistics, which is about source behavior rather than tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.