Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_player

Retrieve a Yahoo Sports player's bio, injury status, physicals, draft info, and current-season stats by league and numeric player ID.

Instructions

Yahoo Sports player detail. Returns one player's bio/overview (position, jersey, status, injury, physicals, college, draft position) plus current-season stats by category, from sports.yahoo.com's own server-rendered player page. The league enum accepts nfl, nba, wnba, mlb, nhl, college-football, college-basketball, college-womens-basketball, mls, premier-league, la-liga, serie-a, bundesliga, ligue-1, nwsl, ligamx-apertura, ligamx-clausura, copa-america, club-world-cup, world-cup, concacaf-champions-cup, concacaf-gold-cup, concacaf-league, and champions-league. Get a numeric player id from a roster response's player url (the last path segment).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
leagueYesLeague key
playerYesNumeric Yahoo Sports player id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / league / enum
      Added value: +[
+  "nfl",
+  "nba",
+  "wnba",
+  "mlb",
+  "nhl",
+  "college-football",
+  "college-basketball",
+  "college-womens-basketball",
+  "mls",
+  "premier-league",
+  "la-liga",
+  "serie-a",
+  "bundesliga",
+  "ligue-1",
+  "champions-league",
+  "nwsl",
+  "ligamx-apertura",
+  "ligamx-clausura",
+  "copa-america",
+  "club-world-cup",
+  "world-cup",
+  "concacaf-champions-cup",
+  "concacaf-gold-cup",
+  "concacaf-league"
+]
  2. Addedv1.14.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist, so the description carries the transparency burden. It discloses the data source ('sports.yahoo.com's own server-rendered player page') and enumerates the returned fields, but it does not mention rate limits, authentication, or failure behavior. For a read-only tool this is adequate but not thorough.

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 description is front-loaded with the purpose and return content, but it spends a long sentence re-listing all league enum values that are already present in the schema. This is redundant and makes the description longer than necessary without adding clarity.

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 two-parameter tool with no output schema and no annotations, the description covers the essential context: what data is returned, the accepted league values, and how to derive the player id. It would benefit from an example or more detail on stats categories, but it is largely complete.

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%, but the description adds real value beyond it: it tells the agent exactly where to get the numeric player id ('from a roster response's player url') and which leagues are valid. The league enumeration repeats the schema enum, but the player-id derivation is genuinely new and useful.

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 one player's bio/overview ... plus current-season stats by category' from a specific source. It clearly distinguishes this from team/roster tools by emphasizing 'one player', though it does not explicitly name sibling alternatives.

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?

There is no guidance on when to use this tool versus alternatives like yahoo_sports_team_roster or fotmob_player. The only usage pointer is how to obtain the player id from a roster response's URL, which is helpful for parameter sourcing but not for tool selection.

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