Retrieve official Cricinfo RSS feeds for news, live scores, country stories, or player stories by providing a valid RSS URL; returns clean feed data.
Read a Cricinfo RSS feed. Returns a Cricinfo RSS feed. url must be one of Cricinfo's official news, live-score, country-story, or player-story RSS URLs.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Official Cricinfo RSS feed URL |
Changes observed during successful MCP inspections.
v1.16.2Does 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 discloses output format (an RSS feed) and an input restriction (only official Cricinfo RSS URLs), which is genuinely useful, but says nothing about error behavior for invalid URLs, rate limits, or freshness. Adequate but far from complete for a tool with zero annotation coverage.
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?
The opening two sentences are redundant, a tautology that restates the name and then restates the first sentence. The third sentence, which carries the real constraint, is useful and front-loaded, but the wasted verbosity dilutes the definition.
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?
For a single-parameter read tool with no output schema, the definition covers purpose, input constraint, and output type. It stops short of telling the agent which specific feeds exist or how to obtain valid URLs, leaving a noticeable gap for correct invocation.
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?
Schema coverage is 100% (baseline 3), and the description adds meaning beyond the schema's vague 'Official Cricinfo RSS feed URL' by enumerating the four valid feed categories. It still gives no concrete URL format or example, so it is an increment, not a full clarification.
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 ('Read a Cricinfo RSS feed') and enumerates the feed categories (news, live-score, country-story, player-story) it serves. However, the second sentence ('Returns a Cricinfo RSS feed') merely restates the first, and it never differentiates itself from siblings like cricinfo_news or cricinfo_story.
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 only implied: the constraint that `url` must be an official Cricinfo RSS URL tells the agent what inputs are valid, which indirectly signals the tool fetches feeds. There is no explicit when-to-use guidance and no named alternative (e.g., cricinfo_news, cricinfo_story) for agents comparing siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.