Skip to main content
Glama

SportStatsAPI

Get facts

get_facts
Read-only

Ready fact sentences for a match or team, most important first: form, streaks, records, head-to-head, table and stakes; after a match the story and the runs it ended. Each fact: type, importance, text (lang de, es, it or fr). summary: the top ones as one paragraph. Facts only, no predictions. The same facts as get_match_briefing and get_team_briefing without the data blocks. Part of the Insights feature.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "get_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesmatch or team code (or number)
kindYesmatch or team (tennis: a player); a league: get_league_facts
langNolanguage of team, league and country names: de, es, it or fr (default English)
sportNosport (default soccer; not cricket or table-tennis)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already cover read-only, non-open-world behavior, so the bar is lower. The description adds useful shape information (fact fields type/importance/text, a summary paragraph, supported languages) and a content boundary ('no predictions'). It does not explain why idempotentHint is false or discuss ordering stability across calls, which matters for a non-idempotent read.

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?

Content is front-loaded with the payoff (what facts you get, ranked) before the structural details. The semicolon-chained clauses make it dense and slightly run-on, but every clause carries information about content or output shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 and does: it enumerates the fact categories, the per-fact fields, the summary paragraph, and language behavior. An agent knows what it will receive and which sibling to use instead for data blocks or league facts.

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 schema already documents kind, id, lang and sport, including the league redirection and language defaults. The description adds little parameter meaning beyond restating the match/team scope and the de/es/it/fr set, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete deliverable: ordered fact sentences ('most important first: form, streaks, records, head-to-head, table and stakes') for a match or team, plus post-match story facts. It explicitly distinguishes itself from get_match_briefing and get_team_briefing by noting it returns the same facts 'without the data blocks', and the kind parameter routes leagues to get_league_facts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context is given: use this for facts-only output, and the sibling comparison ('same facts as get_match_briefing and get_team_briefing without the data blocks') tells an agent when to pick this over those. It also states 'Facts only, no predictions', an implicit exclusion. It never spells out an explicit when-not condition in prose, so it falls short of a 5.

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