Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

espn_news

Fetch recent ESPN league news articles by specifying sport and league; returns headlines, descriptions, and links from public JSON.

Instructions

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

Input Schema

TableJSON 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

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full behavioral burden. It discloses that the data is from credential-free public JSON, which is useful. However, it doesn't describe the output format in detail (e.g., whether it returns a list, pagination, number of articles) or potential errors. It adds some behavioral context but not comprehensive.

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 concise and front-loaded, with the purpose stated first. It effectively uses two sentences to convey the tool's function and parameter enums. No fluff or redundant information, though the enum list is long but necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema, the description should explain the return structure. It mentions the article fields (headline, description, link) but not whether it returns a list or how many articles. It also lacks info about pagination or error handling. Overall, it's adequate but incomplete for a tool with no output schema.

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?

The schema provides 100% coverage of parameter descriptions, including enums and the constraint that league must be valid for sport. The description repeats these enums and the constraint, adding no additional meaning beyond the schema. Therefore, it contributes no extra value for parameter understanding.

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 recent news articles (headline, description, link) for a league from ESPN. It specifies the resource (ESPN league news) and the function (returns articles), which is distinct from other ESPN tools like scoreboard or standings. However, it doesn't explicitly differentiate from other news source tools, so it's clear but not perfect.

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 implies usage for retrieving league news from ESPN, but doesn't explicitly state when to use this over alternatives. It provides parameter constraints (league must be valid for sport) but no guidance on when not to use this tool or why choose it over other news tools. The context of sibling tools suggests it, but it's not 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