Skip to main content
Glama

SportStatsAPI

Get league facts

get_league_facts
Read-only

What finished matches changed, newest first: the match story (comebacks, late winners, red cards), runs started or ended, table places and zones, each also as a sentence (lang de, es, it, fr). Answers 'what happened in this league today'. Facts only. Part of the Insights feature.

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_league_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
sinceNoonly matches updated after this RFC 3339 time
sportNosport (default soccer; see list_sports)
league_idNoonly this league (from find_leagues)
min_importanceNoonly facts of at least this importance, 0-100 (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / league_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / league_id / description
      Previous value: -"only this league (from list_leagues)"New value: +"only this league (from find_leagues)"
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds real behavioral value on top by specifying result ordering ('newest first'), the exact fact categories returned, and that each fact is also rendered as a localized sentence. 'Facts only' usefully distinguishes the output from narrative prose. It stops short of stating volume limits or whether results are bounded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with what is returned and the ordering, then the content taxonomy, then the usage framing. Dense but each clause carries information. The telegraphic style ('runs started or ended', 'each also as a sentence') is slightly compressed at the cost of easy parsing, and 'Part of the Insights feature' adds little for an agent.

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 no output schema, the description carries the burden of explaining return values and does so by enumerating the fact types and noting the sentence rendering. All parameters are optional and fully described in the schema, so calling it correctly is straightforward. The remaining gap is result volume/pagination, which matters for a 'newest first' feed.

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%, so all five parameters (lang, since, sport, league_id, min_importance) are already documented. The description only echoes the language values and hints at recency via 'today'; it adds nothing about how min_importance filtering shapes the fact mix or how since interacts with 'newest first'. Baseline 3 is appropriate.

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?

The description names a concrete resource and enumerates its content: match story elements (comebacks, late winners, red cards), runs started/ended, table places and zones, ordered newest-first. An agent can tell this returns editorial-style insight facts about finished matches rather than raw match data. It does not, however, distinguish itself from the sibling get_facts, and 'Part of the Insights feature' is product framing rather than a scope statement.

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?

'Answers "what happened in this league today"' gives one clear usage scenario, which is helpful. But there are no exclusions, no stated prerequisites, and no named alternative (e.g. get_facts, get_summary, get_match_briefing) for when an agent wants raw results or a prose briefing instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources