Skip to main content
Glama

SportStatsAPI

Get match briefing

get_match_briefing
Read-only

Ready briefing for one match (any sport but cricket): form, current streaks, home and away records, head-to-head, table position and gaps, stakes, schedule; for soccer also injuries, lineups, players one league appearance or goal short of a club milestone (milestone_next) and, after the match, the story (comeback, late winner, red cards), runs it ended (streak_ended_*: 'first defeat after 11 unbeaten') and long waits it ended that our data can date (first_since_*: first win at the opponent's ground, first clean sheet, top of the table for the first time since a day; history_from: nothing is claimed before it). The head-to-head block has goals and each side's biggest win. Soccer before kickoff: players suspended (suspended_out) or one booking from a ban, by the league's card rules. Each statement also as a sentence (lang de, es, it, fr), and summary: the most important sentences as one paragraph in that language. Facts only, no predictions. 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": {
      "match_id": "<match_id>"
    },
    "name": "get_match_briefing"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
sportNosport (default soccer; see list_sports)
formatNomd for a short Markdown text instead of JSON
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?

Beyond readOnlyHint=true, the description discloses real behavioral traits: it refuses cricket, is factual with no predictions, localizes statements and summary into de/es/it/fr, and — importantly — defines epistemic bounds via 'history_from: nothing is claimed before it' so the agent knows claims are date-limited. It also notes milestone/ban thresholds are league-rule driven. It does not describe response size or what happens for unsupported sports beyond cricket.

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

Conciseness5/5

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

Verbose on the surface, but with no output schema the enumerated block names (milestone_next, streak_ended_*, first_since_*, history_from, suspended_out) are load-bearing contract information, and the core purpose is front-loaded in the first six words. The semicolon-delimited grouping of pre-match vs post-match content keeps it navigable despite its length.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with a large, variable, undocumented response, the description does a reasonable job enumerating what comes back and which sections are soccer-only. However, it never states that content varies by sport and match state in a way the agent can plan around (e.g., what a non-soccer, non-football briefing contains), and there is no mention of size or error behavior for cricket.

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 the schema already defines lang, sport, format and match_id. The description adds only modest meaning on top — that lang also governs the prose of each statement and the summary paragraph, and that soccer is the assumed default with richer soccer-only content. 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 opening clause states a specific verb and resource — 'Ready briefing for one match' — and immediately scopes it ('any sport but cricket'), then enumerates the content blocks (form, streaks, head-to-head, table gaps, stakes). It is clearly an aggregated narrative/insight product rather than raw match data, which implicitly separates it from get_match/get_match_details, though no sibling is ever named.

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 conditions are implied rather than stated: 'Soccer before kickoff' and 'after the match' signal temporal applicability, and 'Facts only, no predictions' plus 'Part of the Insights feature' hint it is the analytical layer. There is no explicit instruction such as 'use get_match_details instead when you only need lineups/score', so the agent must infer the boundary from sibling names alone.

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