Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

espn_standings

Fetch ESPN league standings grouped by conference or division for football, basketball, baseball, hockey, and soccer.

Instructions

ESPN standings. Returns league standings grouped by conference/division from ESPN's credential-free public JSON. 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

TableJSON 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.4/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It usefully states that the data comes from ESPN's credential-free public JSON and that results are grouped by conference/division, implying no authentication and a read-only operation. However, it omits details about response structure, pagination, or rate limits.

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 core purpose in the first line and then provides parameter context. It is somewhat long due to repeating the full enum lists from the schema, but every sentence contributes useful information and there is no filler.

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 retrieval tool with four parameters and no output schema, the description covers the main points: what is returned, grouping, valid parameter values, and the sport/league constraint. It does not discuss usage context or alternatives, but the essential facts an agent needs to invoke it correctly are present.

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 description coverage is 100%, so the baseline is 3. The description goes further by enriching the schema: it gives human-readable meanings for seasontype values (preseason, regular season, postseason) and explicitly states the league must be valid for the chosen sport. This adds real semantic value beyond the raw enum lists.

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 clearly states the tool returns league standings grouped by conference/division, with a specific verb and resource. It does not explicitly differentiate itself from sibling tools like espn_rankings or other standings tools, but the resource and grouping detail make the purpose clear.

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 guidance on when to use this tool over alternatives, nor any exclusions. It mentions the data source is credential-free but does not tell an agent when to choose espn_standings versus espn_scoreboard, espn_rankings, or other standings tools.

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