Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_rss_feed

Fetch every item from a Yahoo Sports RSS feed by catalog feed key, returning full content:encoded HTML plus creator and publisher metadata without added limits or date filters.

Instructions

Yahoo Sports RSS feed. Returns every item in one Yahoo Sports RSS feed, including full content:encoded HTML and creator/publisher metadata when present. Feed keys come from yahoo-sports-rss-catalog; no caller limit or date filter is added.

Input Schema

NameRequiredDescriptionDefault
feedYesFeed key from yahoo-sports-rss-catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.5/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 disclosure burden. It does disclose behavioral traits beyond the schema: returns ALL items with no caller limit or date filter, and includes content:encoded HTML plus creator/publisher metadata. It does not cover auth, rate limits, or failure behavior, leaving gaps for a fetch tool.

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?

Three short sentences, front-loaded with the core behavior and followed by content detail and the key-source constraint. Every sentence adds something, though the phrasing is slightly dense with parenthetical clauses.

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 one-parameter, annotation-free fetch tool with no output schema, the description covers what is returned (all items, full HTML, metadata) and what is not applied (limit/date filter). Enough for an agent to call it correctly, though it omits any error or empty-feed behavior.

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%, so the single feed parameter is already fully documented. The description's only added assertion, that feed keys come from yahoo-sports-rss-catalog, merely repeats the schema's own parameter description. Baseline 3 is appropriate when the schema does the work.

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 every item in one Yahoo Sports RSS feed, including full content. This distinguishes it from the catalog sibling by naming yahoo-sports-rss-catalog as the source of feed keys. Slight ambiguity remains because 'RSS feed' is generic against the many yahoo_sports_news-style siblings in this namespace.

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?

Implicitly routes the agent to yahoo-sports-rss-catalog for the required feed key, which is useful usage context. However, it never states when to choose this over sibling tools like yahoo_sports_news or yahoo_sports_section_stream, nor any prerequisites.

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