get_news_feed
Retrieves local and national news from RSS feeds, delivering headlines and stories for your region and country.
Instructions
Local and national news
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Retrieves local and national news from RSS feeds, delivering headlines and stories for your region and country.
Local and national news
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description must disclose behavior, but it provides none. It doesn't indicate whether the tool returns a list, requires network access, or has any side effects. The statement 'Local and national news' is purely descriptive and adds no behavioral context.
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?
While the description is extremely brief, it omits essential information, making it under-specified rather than concise. It is a short phrase without any structuring or explanatory content.
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 has no annotations or output schema, so the description is the only source of context. It fails to explain what the news feed contains, how it is returned, or how it relates to the sibling tools. A simple statement of scope is insufficient for a minimally viable description.
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 the schema is empty and the description need not explain parameter usage. Baseline 4 is appropriate, although the description does not add parameter-specific semantics.
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 description 'Local and national news' is a vague noun phrase that does not clearly state an action or resource. It fails to specify that the tool retrieves or lists news feeds, and does not differentiate from siblings beyond topic. The name implies a feed, but the description is a tautology of the name.
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 usage guidance is provided. There is no mention of when to use this tool versus the sibling feeds (fetch_rss, get_tech_feed, etc.), nor any context for selecting it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jeffgbradley2/rss-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server