Skip to main content
Glama

SportStatsAPI

Get match details

get_match_details
Read-only

Detail of one match: statistics or box score, lineups, injuries (soccer: per player type, expected_return and matches_missed; null = not known), play-by-play, a cricket scorecard (batting, bowling, fall of wickets), rugby scoring events, esports maps and games with player lines, or the singles and doubles of a table tennis team match with set scores.

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>",
      "part": "<part>"
    },
    "name": "get_match_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNolanguage of team, league and country names: de, es, it or fr (default English)
partYesstats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football, as the source sends them); box_score or plays (soccer, basketball, hockey, baseball, american-football: our own typed format, the same for every league, best for analysis); stats (volleyball box score: top leagues of 14 European federations); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)
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 / part / description
      Previous value: -"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football, as the source sends them); box_score or plays (basketball, hockey, baseball, american-football: our own typed format, the same for every league, best for analysis); stats (volleyball box score: top leagues of 14 European federations); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)"New value: +"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football, as the source sends them); box_score or plays (soccer, basketball, hockey, baseball, american-football: our own typed format, the same for every league, best for analysis); stats (volleyball box score: top leagues of 14 European federations); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)"
  2. Changed1 schema field changed
    • changedInput schema / properties / part / description
      Previous value: -"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football, as the source sends them); box_score or plays (basketball: our own typed format, the same for every league, best for analysis); stats (volleyball box score: top leagues of 14 European federations); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)"New value: +"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football, as the source sends them); box_score or plays (basketball, hockey, baseball, american-football: our own typed format, the same for every league, best for analysis); stats (volleyball box score: top leagues of 14 European federations); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)"
  3. Changed1 schema field changed
    • changedInput schema / properties / part / description
      Previous value: -"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); stats (volleyball box score: top leagues of 14 European federations); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)"New value: +"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football, as the source sends them); box_score or plays (basketball: our own typed format, the same for every league, best for analysis); stats (volleyball box score: top leagues of 14 European federations); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)"
  4. Changed1 schema field changed
    • changedInput schema / properties / part / description
      Previous value: -"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)"New value: +"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); stats (volleyball box score: top leagues of 14 European federations); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)"
  5. 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"
  6. Changed1 schema field changed
    • changedInput schema / properties / match_id / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "string"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / part / description
      Previous value: -"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines)"New value: +"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines); games (table-tennis: singles and doubles with set scores)"
  8. Changed1 schema field changed
    • changedInput schema / properties / part / description
      Previous value: -"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards)"New value: +"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards); maps (esports: per map or game with player lines)"
  9. Changed1 schema field changed
    • changedInput schema / properties / part / description
      Previous value: -"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); scorecard (cricket)"New value: +"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); scorecard (cricket); events (rugby, rugby-league: tries, conversions, penalties, cards)"
  10. Changed1 schema field changed
    • changedInput schema / properties / part / description
      Previous value: -"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football)"New value: +"stats, lineups or injuries (soccer); stats (box score) or play_by_play (basketball, baseball, hockey, tennis, american-football); scorecard (cricket)"
  11. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With readOnlyHint=true and openWorldHint=false already supplied, the description still adds real behavioral context: 'as the source sends them' versus 'our own typed format, the same for every league, best for analysis' tells the agent there are two divergent payload shapes for the same part with different analytic trade-offs. It also discloses that injury values may be null (not known) and that coverage is uneven by sport ('top leagues of 14 European federations' for volleyball). It does not say what happens when a part is unsupported for the given sport, which is the main remaining gap.

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?

It is a single front-loaded sentence with no filler, which is good, but it is an overlong run-on with stacked parentheticals and it spends most of its length restating the 'part' parameter values already in the schema. Trimming the duplication would make the genuine value-add (format trade-offs, null handling) far more visible.

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?

With no output schema, the description carries the burden of describing returns, and it does so unevenly: injuries and esports/table-tennis payloads are specified in detail while stats, box_score and play_by_play returns are only named. It also omits error behavior for invalid sport/part combinations and any note on payload size or rate limits, so an agent still has meaningful unknowns before calling.

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 all four parameters, and much of the description's content list duplicates the 'part' enum text almost verbatim. It does add meaning in a couple of places (null injuries, per-player-type breakdown with expected_return and matches_missed, the raw-versus-typed format choice), but 'sport', 'match_id' and 'lang' are left entirely to the schema. 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 states the resource ('one match') and enumerates the concrete payloads available (stats/box score, lineups, injuries, play-by-play, scorecard, events, maps, games), which lets an agent distinguish it from lighter siblings like get_match_briefing or get_summary. It falls short of a 5 because the framing is a noun fragment ('Detail of one match: ...') rather than an explicit verb+scope statement, and no sibling is named.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing says whether to call get_match, get_match_briefing, or get_summary first, or when this heavier detail call is warranted. The content list implies it is the deep-dive tool, but the agent must infer that, and no exclusions or prerequisites are given.

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