Skip to main content
Glama

SportStatsAPI

Get match

get_match
Read-only

One match: teams, score, status, events (goals, cards...), venue, referee; where known TV channels by country and, after the match, a highlights video link. Soccer adds timeline: the events normalised (minute, extra_minute, team home/away, kind goal, penalty, own_goal, missed_penalty, yellow, second_yellow, red, substitution or var, player, assist, player_in/player_out, detail: card reason or VAR outcome; minute null = not known; no headers or xG per shot: not in our data) and referee_stats: the referee's season in the league (games, cards and penalties per game, with league_matches_with_referee of league_matches_played). Matches with a page on our website (soccer, basketball, hockey, tennis, volleyball, handball, baseball, American football, cricket): summary, ready paragraphs on the match from our data (table places, form, meetings, season; cricket: the result, the innings, the best performances, before the start form and meetings in the format), with key_facts before kick-off and what_it_means after the result, summary_as_of when written; only until kick-off and once finished, English only (no lang). Facts only, no predictions.

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": {
      "sport": "<sport>",
      "match_id": "<match_id>"
    },
    "name": "get_match"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
sportYessport (see list_sports)
match_idYesmatch code (or number) from get_matches

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / match_id / description
      Previous value: -"match id from get_matches"New value: +"match code (or number) from get_matches"
  2. Changed1 schema field changed
    • changedInput schema / properties / match_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only cover read-only and non-open-world behaviour, and the description adds real context beyond them: field availability windows (summary only before kick-off and after the result), the language restriction on those summaries, which sports have site pages, and explicit data limits ('no headers or xG per shot: not in our data', 'minute null = not known'). It still omits error behaviour for unknown match ids and whether absent fields are null or simply missing, so it stops short of full disclosure.

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

Conciseness3/5

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

The content is front-loaded (what one match returns comes first, before the soccer and site-page specifics), which is correct. However, it is delivered as one sprawling semicolon-and-parenthesis chain with deeply nested asides, making the scope of each clause hard to parse at a glance. The information earns its place, but the packaging does not.

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 full burden of explaining return values, and it does so thoroughly across sports, including enum-like event kinds and referee_stats shape. The main remaining gap is the absence of any distinction from the near-named siblings get_match_details and get_match_briefing, which is exactly the ambiguity a complex tool needs resolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description does add meaning on top: it ties sport to the site-page coverage list and constrains lang by noting summaries are 'English only (no lang)'. It also frames match_id as coming from get_matches, consistent with the schema. The gain is modest but real, so a 4 rather than the baseline 3.

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 opening clause names a concrete resource and enumerates its payload: teams, score, status, events, venue, referee, TV channels and highlights. That is specific enough for an agent to know this returns a single match, plus soccer-only extras (timeline, referee_stats) and site-page summaries. It never names a sibling such as get_match_details or get_match_briefing, so the agent must infer the boundary itself.

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?

Usage is implied by the content list (fetch one match by id from get_matches) and by conditional notes: 'only until kick-off and once finished, English only (no lang)' and 'after the match, a highlights video link'. These are useful conditional facts but read as return-value caveats rather than when-to-use routing. No exclusions or alternatives are stated, so an agent cannot tell when to prefer get_match_details or get_match_briefing.

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