Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

espn_scoreboard

Fetch game scores, schedules, status, and available odds from ESPN for a selected sport and league by date, week, or season type.

Instructions

ESPN scoreboard. Returns games (scores, schedule, status, and odds when available) for a sport and league. The sport enum accepts football, basketball, baseball, hockey, and soccer. The league enum accepts nfl, college-football, nba, wnba, mens-college-basketball, womens-college-basketball, mlb, nhl, eng.1, esp.1, ita.1, ger.1, fra.1, usa.1, and uefa.champions; it must be valid for the chosen sport. The seasontype enum accepts 1 (preseason), 2 (regular season), 3 (postseason), and 4 (offseason).

Input Schema

NameRequiredDescriptionDefault
weekNoWeek number (football leagues)
datesNoDate or range as YYYYMMDD, YYYYMMDD-YYYYMMDD, or YYYY; defaults to the current scoreboard
sportYesSport key
leagueYesLeague key (must be valid for the sport)
seasontypeNoSeason type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / league / enum
      Added value: +[
+  "nfl",
+  "college-football",
+  "nba",
+  "wnba",
+  "mens-college-basketball",
+  "womens-college-basketball",
+  "mlb",
+  "nhl",
+  "eng.1",
+  "esp.1",
+  "ita.1",
+  "ger.1",
+  "fra.1",
+  "usa.1",
+  "uefa.champions"
+]
    • addedInput schema / properties / seasontype / enum
      Added value: +[
+  1,
+  2,
+  3,
+  4
+]
    • addedInput schema / properties / sport / enum
      Added value: +[
+  "football",
+  "basketball",
+  "baseball",
+  "hockey",
+  "soccer"
+]
  2. Addedv1.5.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral disclosure. It does mention that odds are returned 'when available' and that the league 'must be valid for the chosen sport,' which are useful constraints. However, it omits details about rate limits, authentication, output format, and pagination, leaving significant behavioral gaps.

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 front-loaded with the tool's purpose and then lists enum values, which is structured and readable. However, the extensive enumeration of sport, league, and seasontype values is somewhat verbose given that the schema already contains this information, making it less concise than ideal.

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?

There is no output schema, so the description should explain return values. It does so briefly: games with scores, schedule, status, and odds when available. It also covers all parameter enums and a cross-parameter constraint. The main gap is the lack of return structure details (e.g., array format) and usage context relative to siblings, but it is largely complete for the tool's complexity.

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 the schema already documents all parameters. The description adds enum value listings and the cross-constraint that league must be valid for the chosen sport, but this largely duplicates schema content. The baseline score of 3 applies 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Returns games (scores, schedule, status, and odds when available) for a sport and league.' It clearly identifies the tool's function but does not distinguish it from sibling tools like espn_game_summary or espn_standings, which also return game-related data.

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?

The description provides no explicit guidance on when to use this tool versus alternatives such as espn_game_summary, espn_standings, or other scoreboard tools. It only implies usage through required parameters (sport and league) without mentioning exclusions or scenarios when another tool is more appropriate.

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