Skip to main content
Glama
christianclaudio

io.github.christianclaudio/espn

by christianclaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Games Get Team Schedule

games_get_team_schedule
Read-onlyIdempotent

Fetch a team's season schedule and results, including opponents, scores, dates, home/away status, and event IDs. Use season_type=3 for postseason games.

Instructions

Fetch a team's season schedule and results: opponents, scores, dates, home/away, and event IDs. Regular season by default; season_type=3 for postseason games (e.g. the World Series, NBA Finals, or Super Bowl).

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

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds the default scope (regular season) and the season_type=3 postseason switch, plus the returned data fields, but says nothing about pagination, rate limits, or authentication needs. This is useful but modest added context given the rich annotations.

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 sentences, front-loaded with the core operation and return fields, followed by the season_type default. Every clause earns its place with no redundancy.

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 read-only schedule tool with no output schema, the description helpfully lists the returned fields and explains the season_type default. The main gap is that team_id format or source is never mentioned, even though it is required. Otherwise the definition is complete enough given the annotations and schema coverage.

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 80%, so the schema already documents sport, league, season, and season_type. The description mostly duplicates that information with postseason examples and adds no format guidance for team_id, which remains undocumented in both schema and description. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb ('Fetch') and resource ('team's season schedule and results'), and enumerates the returned fields (opponents, scores, dates, home/away, event IDs). This makes it clearly distinct from sibling tools like games_get_scoreboard or games_get_game_summary without needing to name them explicitly.

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?

The description gives usage context for the season_type parameter ('Regular season by default; season_type=3 for postseason games'), but it never says when to choose this tool over siblings like games_get_scoreboard or games_get_league_events. Usage is implied by the tool's purpose, but there is no explicit when-to-use or when-not-to-use guidance.

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

Deploy Server

Other Tools