Skip to main content
Glama
io.github.christianclaudio/espn

io.github.christianclaudio/espn

Games Get Scoreboard

games_get_scoreboard
Read-onlyIdempotent

Fetch final or live scores, game status, and event IDs for any date, sport, and league, including postseason games; use it to check if a team played on a specific date.

Instructions

Fetch final scores and results for any date, including postseason games such as the Super Bowl, World Series, or NBA Finals, plus live scores, game status, periods/innings, clocks/outs, TV broadcasts, and probable starters. Returns each game's event ID. Filter by date, week, season type, or Top 25 group. Sports: football, basketball, baseball, hockey, soccer, golf, mma. Use this first to check whether a team played on a particular date; provide the date, sport, and league, and no team ID is needed. Both sport and league are required; for NFL, use sport='football' and league='nfl'. Results are capped by limit (default 50); raise limit on busy dates. For Division I men's college basketball, pass group='50'. Before concluding that a team did not play, check the team's schedule.

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>",
      "league": "<league>"
    },
    "name": "games_get_scoreboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYYMMDD, e.g. 20161102; omit for today. Or an inclusive range YYYYMMDD-YYYYMMDD, e.g. 20260919-20260925 (up to 31 days; golf: any length). Outside golf a range is fetched day by day: limit applies to each day, so up to 31 times limit events, and one failed day fails the whole call.
weekNo
groupNo
limitNo
sportYese.g. basketball
leagueYese.g. nba, eng.1
season_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / date / description
      Previous value: -"YYYYMMDD, e.g. 20161102; omit for today."New value: +"YYYYMMDD, e.g. 20161102; omit for today. Or an inclusive range YYYYMMDD-YYYYMMDD, e.g. 20260919-20260925 (up to 31 days; golf: any length). Outside golf a range is fetched day by day: limit applies to each day, so up to 31 times limit events, and one failed day fails the whole call."
  2. Changed3 schema fields changedv2.0.0
    • addedInput schema / properties / date / description
      Added value: +"YYYYMMDD, e.g. 20161102; omit for today."
    • addedInput schema / properties / league / description
      Added value: +"e.g. nba, eng.1"
    • addedInput schema / properties / sport / description
      Added value: +"e.g. basketball"
  3. First observedv1.2.9

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the main burden is met. The description still adds useful operational context beyond the annotations: results are capped by limit (default 50) and limit should be raised on busy dates, and each game's event ID is returned. It does not discuss the day-by-day range failure mode or pagination behavior, which limits it to a 4.

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?

The description is dense and front-loads the purpose and return data before moving to filtering and invocation rules, so the important content comes first. It is a long run-on paragraph covering many topics, which slightly hurts scanability, but almost every sentence contributes usable guidance.

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?

For a 7-parameter read tool with no output schema, the definition covers purpose, required inputs, key filters, result caps, and routing to the team schedule for negative results. The main gap is the unexplained week and season_type parameters and lack of guidance on the day-by-day range semantics, which the description leaves entirely to the schema.

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 only 43%, so the description must compensate, and it does for most parameters: date (implied 'any date' plus 'provide the date'), required sport/league with a concrete NFL example, group='50' for Division I men's basketball, and limit default/behavior. However, week and season_type are never explained, leaving two parameters undocumented in both schema and description.

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?

States a specific verb and resource: fetch final scores/results for any date, plus live scores, status, periods, broadcasts, and probable starters, with event ID returned. It is clear about scope and coverage, but it does not explicitly distinguish itself from the sibling games_get_scoreboard_header, so it falls short of a 5.

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

Usage Guidelines5/5

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

Explicitly tells the agent to use this first to check whether a team played on a date, that no team ID is needed, and to check the team's schedule before concluding a team did not play, which routes to the sibling tool. It also gives concrete invocation rules (both sport and league required, NFL maps to sport='football'/league='nfl', group='50' for Division I men's basketball).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.