Retrieve current Denver Post headlines for a chosen section or topic archive. Provide a section slug to fetch structured editorial headlines from news, sports, opinion, and more.
Get Denver Post section headlines. Returns current headlines from one public editorial section or topic archive.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Section or topic slug returned by denverpost-sections |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It says headlines are 'current' but does not disclose pagination, result limits, sorting, caching, whether results refresh, or whether an auth requirement exists. For a public news-feed tool with no annotations, that is a significant transparency gap.
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, both front-loaded with the core action and scope. No filler, though the second sentence ('topic archive') is slightly redundant with the first.
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 single required enum param with 100% schema coverage and no output schema, the definition is adequate to invoke correctly. But with no annotations and no output schema, it should describe the shape of the returned headlines and any pagination or freshness behavior, which it omits.
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?
Schema description coverage is 100%, with a documented enum whose description points back to denverpost-sections. The description adds little beyond what the schema already documents. Baseline 3 is appropriate because the schema does the parameter work.
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 states a specific verb and resource: 'Get Denver Post section headlines,' and adds scope ('one public editorial section or topic archive'). It clearly distinguishes itself from the sibling denverpost_news/denverpost_article by implying a list-of-headlines shape rather than a full article fetch. It doesn't explicitly name the sibling alternative, but the resource is unambiguous.
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 implies when to use it (to get headlines for a section) but gives no explicit when-not or mention of the trading-off siblings such as denverpost_news or denverpost_sections. An agent must infer that sections come from denverpost_sections, though the param description does say the slug is 'returned by denverpost-sections'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.