Skip to main content
Glama

Game

get_game
Read-onlyIdempotent

Use for one match in full: score (with shootout), both clubs' box scores (possession, shots, xG, passing, discipline), every player's line, the key events (goals, cards, substitutions, penalties, VAR) and each sportsbook's opening and closing line. For every event use get_events; for formations use get_lineups. Costs 5 credits. Prices are market information; no tool places, accepts or tracks wagers.

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": {
      "game_id": "<game_id>"
    },
    "name": "get_game"
  }
}

Input Schema

NameRequiredDescriptionDefault
leagueNoLeague. Defaults to soccer. One of: soccer, mls, laliga, seriea, bundesliga, ligue1, ucl, championship, nwsl, ligamx, uel, uecl, eredivisie, primeira, scotland, brazil, argentina.
game_idYesMatch id, from list_games or get_schedule.

Output Schema

NameRequiredDescriptionDefault
gameYes
oddsYes
playersYes
key_eventsYes
team_statsYes
box_score_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / game_id / description
      Previous value: -"ESPN match id, from list_games or get_schedule."New value: +"Match id, from list_games or get_schedule."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the bar is lower; the description still adds two non-obvious facts: the call costs 5 credits, and prices are market information with no wagering capability. It does not mention pagination, size limits, or latency for what is clearly a heavy payload.

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?

It is front-loaded with the payload summary, then alternatives, then cost and the wagering disclaimer — every sentence carries information. The middle sentence is a very dense comma-separated list, which is efficient for scanning but borders on run-on.

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?

An output schema exists, yet the description still summarizes the return surface and adds the cost and market-information caveats an agent would otherwise not have. For a two-parameter read tool with full annotation coverage, nothing material needed to call it correctly is missing.

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% and both parameters are fully documented in the schema, including the league enum and the game_id provenance (from list_games or get_schedule). The description adds no parameter-level syntax or format detail beyond that, so the baseline of 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 specific resource (one match in full) and enumerates exactly what comes back: score with shootout, both clubs' box scores, player lines, key events, and sportsbook opening/closing lines. That level of detail distinguishes it from siblings such as get_events and get_lineups without the agent needing to open the schema.

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?

It explicitly routes the agent away for two sub-cases ('For every event use get_events; for formations use get_lineups'), which is real exclusion guidance. It does not state when a whole-match pull is unnecessary (e.g., when a cheaper single-market call like get_odds would suffice), so the alternative landscape is only partially covered.

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.