Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

denverpost_news

Fetch Denver Post top stories as structured article cards with title, URL, summary, author, publication time, image, and type to monitor current headlines.

Instructions

Get Denver Post top stories. Returns the article cards on the Denver Post homepage, about 91 when last checked, though the count varies as the site updates. Each item has a title and URL and can carry a summary, author, publication time, image and type. It takes no parameters.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden and does reasonably well: it discloses that the result is homepage article cards, that the count is variable (~91 when checked), and that optional fields (summary, author, time, image, type) may or may not be present. It omits auth/permission expectations and rate-limit behavior, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then the return shape, then the no-parameter note. Three tight sentences with no filler. The field enumeration is arguably verbose but justified because there is no output schema to document the payload.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-param, no-annotation, no-output-schema tool, the description covers what an agent needs: what comes back, roughly how many items, and which fields are optional. Nothing essential is missing given the tool's simplicity; richer detail (pagination, caching, update cadence beyond 'varies') is unnecessary here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The explicit 'It takes no parameters' is redundant with the empty schema but confirms there is no filtering input, which is mildly useful for an agent deciding whether it needs a query argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get Denver Post top stories') and pins down the source as the homepage article cards, which separates it from an individual article. It does not name its siblings (denverpost_headlines, denverpost_article, denverpost_sections), so an agent must infer the boundary, but the purpose itself is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'top stories' and 'homepage cards' suggest a feed-browsing use case, and 'it takes no parameters' hints at a fire-and-forget call. There is no explicit when-to-use guidance or contrast against denverpost_headlines/denverpost_article, which is where an agent would most likely get confused.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools