Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

espn_standings

Retrieve league standings grouped by conference or division from ESPN for a selected sport, league, season, and season type.

Instructions

ESPN standings. Returns league standings grouped by conference/division. 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), and 3 (postseason).

Input Schema

NameRequiredDescriptionDefault
sportYesSport key
leagueYesLeague key (must be valid for the sport)
seasonNoFour-digit season year; defaults to the current season
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
+]
    • 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?

No annotations are provided, so the description carries the full behavioral burden. It does disclose the return shape (standings grouped by conference/division), which is useful, but says nothing about read-only semantics, data freshness, pagination, or season-coverage limits. Some value added, but not the full disclosure a no-annotation tool demands.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is correctly front-loaded, but a large portion of the text re-lists the sport and league enums that already appear verbatim in the input schema, which is largely redundant. The season parameter is never mentioned, so the space is spent on duplication rather than the one undocumented parameter.

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?

For a moderate-complexity, 4-parameter tool with a rich schema and no output schema, the description adequately covers purpose, enums, and the return grouping. It is missing any usage routing against the many sibling standings tools, and it omits the season parameter entirely, so an agent gets no guidance on default or override behavior from the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning beyond the bare schema descriptions: it maps seasontype integers to human meanings (1=preseason, 2=regular season, 3=postseason) and flags the cross-parameter constraint that league must be valid for the chosen sport. It repeats the sport/league enum lists that already exist in the schema, but the seasontype mapping is a real addition.

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 gives a specific verb and resource ('Returns league standings grouped by conference/division'), which is concrete enough for an agent to know what it does. It does not, however, distinguish itself from the many sibling standings tools (espn_rankings, mlb_standings, sofascore_standings, yahoo_sports_standings), leaving the agent to infer scope from the espn_ prefix alone.

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 states no when-to-use or when-not-to-use conditions and names no alternatives among the numerous sibling standings tools. The only constraint offered ('it must be valid for the chosen sport') is a validity rule, not routing 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