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

io.github.christianclaudio/espn

Games Get Team Schedule

games_get_team_schedule
Read-onlyIdempotent

Retrieve a team's full season schedule, including past results, upcoming opponents, scores, dates, home/away status, and event IDs; choose regular season or postseason.

Instructions

Fetch a team's full season schedule, including past results, upcoming opponents, scores, dates, home/away, and event IDs. Use this for a team's season, last game, or next game; use the scoreboard for games on a particular date. Regular season by default; season_type=3 for postseason.

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>",
      "team_id": "<team_id>"
    },
    "name": "games_get_team_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
sportYese.g. basketball
leagueYese.g. nba, eng.1
seasonNoYear the season ends (2016 = 2015-16); NFL, MLB: the year played; soccer: the year it starts.
team_idYes
season_typeNo2 or omit: regular season; 3: postseason.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / league / description
      Added value: +"e.g. nba, eng.1"
    • addedInput schema / properties / season / description
      Added value: +"Year the season ends (2016 = 2015-16); NFL, MLB: the year played; soccer: the year it starts."
    • addedInput schema / properties / season_type
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "2 or omit: regular season; 3: postseason."
      +}
    • addedInput schema / properties / sport / description
      Added value: +"e.g. basketball"
  2. First observedv1.2.9

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so safety is covered. The description adds real behavioral context beyond them, namely that regular season is the default and postseason requires season_type=3. It stops short of describing pagination or result volume, which keeps it from a 5.

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?

Two dense sentences: the first front-loads what is returned, the second handles routing and default-season behavior. No filler, no repetition of the title, and the highest-value information leads.

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?

With no output schema, the description carries the return-value burden and does so by naming the fields included in each schedule entry. Combined with explicit usage routing and default-season behavior for a five-parameter tool, an agent has everything needed to call it correctly.

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 80%, so the schema already documents sport, league, season year semantics, and season_type values. The description's 'Regular season by default; season_type=3 for postseason' largely restates the schema's own season_type description and adds no format guidance for team_id, so the baseline 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 opens with a specific verb and resource ('Fetch a team's full season schedule') and immediately enumerates the payload (past results, upcoming opponents, scores, dates, home/away, event IDs), which lets an agent distinguish it from games_get_scoreboard without inspecting any schema.

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?

It gives explicit routing rules: use this for a team's season, last game, or next game, and use the scoreboard for games on a particular date. It also states the default season scope and the season_type=3 exception, so no inference is required.

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