Skip to main content
Glama
lacausecrypto

Sports Hub MCP Server

by lacausecrypto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

espn: Get team schedule

espn_get_team_schedule
Read-onlyIdempotent

Retrieve a team's season schedule, including past results and upcoming games, by specifying sport, league, and ESPN team ID.

Instructions

Get a team's schedule for a season, including past results and upcoming games.

Input Schema

NameRequiredDescriptionDefault
sportYesSport code, e.g. "football", "basketball", "baseball", "hockey", "soccer", "mma", "golf", "tennis", "racing"
fieldsNoKeys to keep (comma-separated).
leagueYesLeague code, e.g. "nfl", "nba", "mlb", "nhl", "wnba", "college-football", "mens-college-basketball", "eng.1", "usa.1", "ufc", "pga", "atp", "f1"
seasonNoSeason year (e.g. "2024")
team_idYesESPN team ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Keys to keep (comma-separated).",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.3.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety and caching profile is covered. The description adds a modest behavioral detail — that the payload mixes completed results with future fixtures — but says nothing about pagination, season defaults, or whether the season param is required for current-year data.

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?

A single well-formed sentence with the resource and the temporal scope front-loaded and zero filler. It is arguably under-sized rather than over-sized, but nothing is wasted.

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 must convey what comes back; it does so only loosely ('past results and upcoming games'). For a 5-parameter, 3-required tool spanning multiple sports and leagues, it omits season defaults, whether results are ordered, and how it relates to the sibling nhl_get_team_schedule, leaving real gaps.

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%, so every parameter including the enumerated-style examples for sport and league is already documented in the schema. The description only echoes the 'season' concept, adding no syntax, format, or default-value detail beyond what the schema provides. Baseline 3 is correct.

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?

Clear verb+resource ('Get a team's schedule') with a stated scope ('for a season') and content hint ('past results and upcoming games'). It does not distinguish itself from the near-identical sibling nhl_get_team_schedule or from league-specific schedule tools like mlb_get_schedule, leaving the agent to infer that this is the multi-sport ESPN variant.

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?

No when-to-use guidance, no mention of when to prefer this over nhl_get_team_schedule or the league-specific schedule tools in the sibling list, and no stated prerequisites (e.g. that sport/league/team_id must be mutually consistent). Usage is only implied by the tool name.

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