Fetch How-To Geek top stories from its public RSS feed. Retrieve current article teasers and links, not full article text.
Get How-To Geek top stories. Returns current stories from How-To Geek's public RSS feed. Summaries are publisher teasers, not full article text. This feed-only route does not claim a complete section taxonomy or retrieve article bodies.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and discloses the source (public RSS feed), the nature of the content (publisher teasers, not full article text), and the scope limitations (no full bodies, no complete section taxonomy). It does not mention update frequency or attribution requirements, but for a public feed these are minor gaps.
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 sentences, front-loaded with the core purpose, followed by return-content details and limitations. Every sentence adds distinct value with no 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?
Given a zero-parameter RSS feed tool with no output schema or annotations, the description is complete: it explains what the tool returns (teasers, not full text) and what it does not do. An agent has enough to call it correctly and set expectations.
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 there are no parameter semantics to clarify. The baseline for a 0-param tool is 4.
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 ('Get') and resource ('How-To Geek top stories'), and clarifies it is an RSS-feed route rather than a full section or article-body endpoint. This distinguishes it from sibling news tools that return sections or full text.
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?
The description tells the agent this is for top stories from the public RSS feed and explicitly excludes full article text and complete section taxonomy. However, it does not name an alternative tool to use when full articles or a section taxonomy are needed, so the when-not is present but alternatives are not.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.