Loading ToolBench

Reading the current corpus…

mcp-server-espn MCP server · D · ToolBench

← Browse

mcp-server-espn

github.com/christianclaudio/mcp-server-espn

Model Context Protocol (MCP) server for live & historical sports stats, odds, and schedules via ESPN

2026-07-28+STDIO33 tools

51/100

Definition Quality56

Protocol Readiness44

Supportability47

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

ESPN MCP server has 33 well-named tools with consistent verb_noun patterns (games_get_*, teams_get_*, news_get_*). All tools include descriptions (avg ~60 chars, baseline 194 chars) and input schemas with typed parameters. However, descriptions are significantly shorter than production baselines and lack actionable context (WHEN to use, dependencies, error recovery). Parameter descriptions are minimal (avg ~30 chars vs baseline 72 chars). Output schemas are not documented in visible code. No evidence of pagination support despite tools returning lists (scoreboard, standings, news). Error handling and recovery guidance absent. Tool composition is sound (single responsibility, proper naming), but descriptions need expansion to meet LLM-optimization standards.

Tools (33)

games_get_calendarread only50/100

Get calendar of games and events

games_get_event_oddsread only50/100

Get betting odds for an event

games_get_futuresread only50/100

Get futures and season-long betting odds

games_get_game_predictorread only50/100

Get game prediction data

games_get_game_situationread only50/100

Get current game situation and context

games_get_game_summaryread only50/100

Get detailed game summary including odds, boxscore, and play-by-play

games_get_leaders_by_athleteread only50/100

Get statistical leaders by athlete

games_get_leaders_by_teamread only50/100

Get statistical leaders by team

games_get_league_draftread only50/100

Issues (5)

HIGHtool-description ↗

Tool descriptions are 40-60 characters, well below production baseline of 194 chars. Descriptions lack WHEN to use, dependencies, and error recovery guidance. Example: 'Get live scoreboard with games, scores, and schedules' does not explain when to call this vs games_get_league_events, or what fields are returned.

games_get_scoreboardgames_get_game_summarygames_get_standingsteams_get_teamnews_get_news

HIGHconstrained-input ↗

Parameter descriptions are minimal (avg 30 chars vs baseline 72 chars). Many lack format/constraint guidance. Example: 'sport' param has description 'Sport type (e.g., football, basketball, baseball)' but does not state valid enum values, whether it accepts 'nfl' or 'football', or if it is case-sensitive.

games_get_scoreboardgames_get_game_summarygames_get_team_schedulegames_get_standingsteams_search

HIGHpaginated-result ↗

Recommendations

Expand all tool descriptions to 100-200 characters. Include: (1) what the tool returns, (2) when to use it instead of similar tools, (3) any prerequisites. Example: 'Get live scoreboard for a league. Returns games, scores, and schedules. Use this to see current/upcoming games; use games_get_team_schedule for a specific team's history. Requires valid sport and league identifiers.'
Add enum constraints to sport and league parameters. Document valid values explicitly: sport: enum [football, basketball, baseball, hockey, soccer]; league: enum [nfl, nba, mlb, nhl, mls]. Replace 'e.g.' examples with formal constraints.
Document output schemas for all tools. For list-returning tools (scoreboard, standings, news), specify: (1) fields in each item, (2) pagination support (limit, offset, total_count or next_cursor), (3) max result size. Example: 'Returns array of game objects with fields: event_id, home_team, away_team, score, status. Supports limit (1-100, default 20) and offset pagination.'
Add error recovery guidance to parameter descriptions. Example for event_id: 'Event identifier (string). If unknown, call games_get_scoreboard first to retrieve valid event IDs for the league.'
Verify tool annotations (readOnlyHint=true, destructiveHint=false) are properly registered in fastmcp @mcp.tool() decorators. The check_tool_contract.py script validates them, but they must be visible in the tool definition code.

Spec posture evidence

Inferred effective spec: 2026-07-28+.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

51/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	51	2026-07-28+	v2