Fetch top stories from Liverpool Echo's public home RSS feed. Returns fresh article headlines and summaries, excluding photo galleries that lack readable article bodies.
Get Liverpool Echo top stories. Returns fresh Liverpool Echo top stories from the public home RSS feed. Photo galleries are omitted because they have no readable article body.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description must disclose behavior. It states that photo galleries are omitted due to lack of readable article body, which is a valuable behavioral detail. It also indicates the source is the public home RSS feed, but doesn't mention pagination, rate limits, or response structure.
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?
Two sentences, front-loaded with the main purpose, no extraneous detail. Each sentence adds value.
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 no-parameter read-only tool, the description is largely complete: it states the resource, source, and a known exclusion. However, it doesn't describe the output format or any limitations beyond the gallery omission, which for an agent might be sufficient but not exhaustive.
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 has zero parameters and the schema is empty, so there is nothing to describe. Baseline 4 is appropriate since the description doesn't need to explain parameters.
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?
Description states a specific action: 'Get Liverpool Echo top stories' and clarifies it comes from the public home RSS feed. It distinguishes from sibling tools like liverpoolecho_headlines by emphasizing 'top stories' and the feed source, though it doesn't explicitly name alternatives.
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?
Provides context that it returns fresh top stories from the home RSS feed, implying it's the general news feed. However, it does not explicitly state when to use this over liverpoolecho_headlines or other sections, leaving some ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.