Retrieve SFGATE top stories from its public RSS feed and return fresh headlines as clean JSON, so you can track current San Francisco Bay Area news without parsing raw feeds.
Get SFGate top stories. Returns fresh SFGATE stories from its public "Top News Stories" 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?
No annotations are provided, so the description must carry the disclosure burden. It does reveal that this is a public RSS feed and that stories are 'fresh,' implying a read-only fetch. But it does not describe output shape, item count, or update behavior, leaving only minimal transparency.
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?
A single front-loaded sentence with no filler. It communicates the action, resource, and source efficiently.
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 zero-parameter RSS feed tool, the description is nearly complete: it names the resource, the source, and the freshness expectation. The only real gaps are sibling differentiation and output details, but neither is critical at this complexity.
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 needs no explanation. The description correctly implies a simple no-input fetch, and the baseline of 4 applies.
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 ('Get SFGate top stories') and identifies the data source (public RSS feed). It is clear, but it does not explicitly distinguish itself from sibling tools like sfgate_headlines or sfgate_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?
Usage is implied through 'top stories' and 'RSS feed,' so an agent can infer when it is appropriate. However, there is no explicit guidance about when to choose this over sibling tools or any when-not-to-use conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.