Fetch current top stories from the Denver Post homepage as structured JSON for news monitoring.
Get Denver Post top stories. Returns current top stories from the public Denver Post homepage.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries full behavioral burden. It implies a public read (source is the public homepage) and that no inputs are needed, but says nothing about result ordering, count, freshness/polling behavior, or response shape — and there is no output schema to fall back on.
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?
Short and front-loaded, with the key resource named in the first clause. The second sentence largely restates the first ('top stories' vs. 'current top stories'), costing a little density.
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 fetch tool this is minimally sufficient, but with no annotations and no output schema the description should say more about what comes back. It also lacks any routing hint against its four denverpost siblings.
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 is nothing for the description to disambiguate; the baseline of 4 applies. The schema is empty and consistent with the description.
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?
Specific verb+resource: fetching Denver Post top stories from the public homepage. It is unambiguous what the tool returns, but it does not distinguish itself from the close sibling denverpost_headlines, which an agent would need to choose between.
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 when-to-use guidance and no mention of alternatives. With denverpost_headlines, denverpost_article, and denverpost_sections all present, the agent gets no signal on which to pick for front-page vs. section vs. article content.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.