Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

espn_team_roster

Retrieve a team's ESPN roster—players with position, jersey, age, and experience—plus head coach using sport, league, and team ID or abbreviation.

Instructions

ESPN team roster. Returns a team's roster (players with position, jersey, age, and experience) plus head coach. 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.

Input Schema

NameRequiredDescriptionDefault
teamYesTeam id (numeric) or abbreviation
sportYesSport key
leagueYesLeague key (must be valid for the sport)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / 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 full burden, and it does disclose the return shape, which is real value for a tool with no output schema. However, it says nothing about failure behavior when sport/league are mismatched, whether data is cached/live, or the freshness of roster/coach data.

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?

Front-loaded with the tool's output, which is good, but the bulk of the text is a verbatim re-listing of the sport and league enums that already exist in the input schema. Roughly half the description is redundant and could be deleted without information loss.

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 three-required-parameter read tool with no annotations and no output schema, the description supplies the missing piece an agent needs most: what the response contains. Only the behavior on invalid sport/league pairs and any pagination or size caveats are left unaddressed.

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% and the schema already states 'League key (must be valid for the sport)', so the description's re-listing of both enum sets and the cross-parameter validity rule adds no meaning beyond the structured fields. Baseline 3 applies; the enum repetition earns no credit.

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?

States a specific verb and resource ('Returns a team's roster') and enumerates the returned fields (position, jersey, age, experience, head coach), which lets an agent distinguish it from sibling summary tools like espn_team or espn_scoreboard. It never names a sibling explicitly, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The purpose implies the usage (fetch a roster), but there is no guidance on when to pick this over espn_team, espn_teams, or yahoo_sports_team_roster, and no prerequisites stated. The one constraint given ('league must be valid for the chosen sport') is a validity rule rather than a usage rule.

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