Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

espn_rankings

Fetch ESPN poll rankings like AP Top 25 for college football and basketball to check current team standings.

Instructions

ESPN poll rankings. Returns poll rankings (e.g. AP Top 25) for a college league. Rankings are only published for college leagues: the sport enum accepts football and basketball, and the league enum accepts college-football, mens-college-basketball, and womens-college-basketball.

Input Schema

NameRequiredDescriptionDefault
sportYesSport key
leagueYesCollege league key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / league / enum
      Added value: +[
      +  "college-football",
      +  "mens-college-basketball",
      +  "womens-college-basketball"
      +]
    • addedInput schema / properties / sport / enum
      Added value: +[
      +  "football",
      +  "basketball"
      +]
  2. Addedv1.5.0

TDQS

A3.7/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. It usefully discloses that rankings exist only for college leagues and names the exact accepted enum values, which is real behavioral context. But it says nothing about what polls are returned, whether rankings are current/seasonal, or the response shape.

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?

Front-loaded with 'ESPN poll rankings' and the constraint example in sentence two. It is efficient, though the third sentence largely repeats the enum values verbatim from the schema.

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 simple two-required-enum retrieval tool with no output schema and no annotations, the description covers purpose, scope constraint, and valid inputs adequately. Return-value details are absent but not strictly required given the tool's simplicity.

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 coverage is 100% and both parameters are documented enums, so the baseline is 3. The description mostly restates the enum values already present in the schema and adds no format or semantic detail beyond them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb (returns) and resource (poll rankings, e.g. AP Top 25) with an explicit scope (college leagues). An agent can distinguish this from the many other ESPN siblings (scores, standings, teams) without opening any schema.

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 description supplies a use constraint ('Rankings are only published for college leagues') which implicitly tells the agent when this tool applies. However, it names no alternatives and does not say what to use for professional leagues, so the guidance is implied rather than explicit.

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