Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

espn_news

Fetch recent ESPN news for a chosen sport and league, returning article headlines, descriptions, and links for quick updates.

Instructions

ESPN league news. Returns recent news articles (headline, description, link) for a league. 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
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

A3.6/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 usefully discloses the return shape (headline, description, link) and the sport/league validity constraint, but says nothing about rate limits, article freshness, result count, or pagination behavior, leaving meaningful gaps.

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 and return fields are front-loaded, which is good, but roughly two-thirds of the text is a verbatim enumeration of enum values already defined in the input schema, which is redundant padding rather than added value.

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?

With only two enum-constrained required parameters, no output schema, and no annotations, the description covers what the tool returns and the cross-parameter validity rule. It is close to complete for a simple list-style news fetcher, though result volume/pagination remains 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% with both params enum-documented, so the baseline is 3. The description restates the same enum members and the same 'must be valid for the sport' constraint already present in the schema, adding no syntax, default, or selection guidance beyond it.

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 news articles) and resource (ESPN league news) and identifies the return fields (headline, description, link). It is clearly distinguishable from siblings like espn_scoreboard, espn_standings, and espn_rankings, which retrieve different data types for the same entity.

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?

Usage is implied by the name and resource but never stated: there is no explicit when-to-use, no when-not, and no routing to sibling news tools (e.g., fotmob_news, foxsports_news, cricinfo_news). An agent can infer intent but must decide alternatives on its own.

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