Retrieve recent FanDuel Research RSS items with channel metadata and summaries for quick sports research updates; linked article pages are not fetched.
FanDuel Research recent RSS items. Returns channel metadata and the recent item summaries from FanDuel Research's official RSS feed. summary is the feed description, not a full article body; this endpoint does not fetch linked article pages.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.16Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It usefully discloses two caveats: `summary` is the feed description rather than article content, and linked article pages are not fetched. It says nothing about item volume, recency window, ordering, or caching, which an agent would want for a feed endpoint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with what the tool is, followed by what it returns and the key caveat. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description sufficiently explains the return shape (channel metadata + item summaries) and pre-empts the main misconception about `summary`. Missing only operational detail such as item count and recency window.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so parameter semantics baseline is 4. The description correctly implies a parameterless fetch and adds no misleading input claims.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: recent RSS items from FanDuel Research, returning channel metadata plus item summaries. It also rules out article-body retrieval, which differentiates it from the article-fetching siblings. It stops short of naming the alternative tool (e.g. fanduel_research_article) explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: use this for a recent-items listing rather than full articles, since it 'does not fetch linked article pages.' However, no alternative tool is named and there is no explicit statement of when to prefer it over fanduel_research_articles or fanduel_research_featured_articles.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.