Retrieve top stories and columns from Townhall's public RSS feed. Get current news and opinion pieces for your application.
Get Townhall top stories. Returns fresh Townhall news and column stories from the public site-wide RSS feed.
| 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?
With no annotations, the description carries the full burden. It discloses that the data comes from a public site-wide RSS feed and that stories are fresh, which suggests a read-only operation and a helpful source context. It does not describe the output shape, number of items, or freshness semantics beyond 'fresh'.
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 short sentences, front-loading the action, with no redundant phrases. 'Fresh' and 'public site-wide RSS feed' add meaningful scope without bloating the text.
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?
The tool is a simple zero-parameter feed fetch, and the description names the source, content type, and scope. It is complete enough for invocation, though the lack of an output schema means field-level return details are not specified.
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, so there is nothing for the description to clarify beyond the schema. Baseline 4 applies because no parameter documentation is needed.
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?
The first sentence 'Get Townhall top stories' names a specific verb and resource, and the second clarifies it returns fresh news and column stories from the public site-wide RSS feed. It is distinguishable from the general pattern, though it does not explicitly contrast with sibling tools like townhall_headlines or townhall_sections.
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?
No guidance is given on when to use this tool versus alternatives in the same Townhall family (e.g., townhall_headlines, townhall_article, townhall_sections). The agent must infer that top stories from the site-wide feed is the intended use, with no exclusions or selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.