Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

chicagotribune_news

Fetch current Chicago Tribune top stories from its homepage without input to get titles, canonical URLs, publication times, bylines, excerpts, and lead images.

Instructions

Get Chicago Tribune top stories. Returns the current Chicago Tribune top stories from its homepage, with no input needed. Each has a title and canonical article URL, plus publication time, byline, excerpt and lead image where the story card shows them.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full disclosure burden. It does usefully describe the source (homepage) and the returned fields (title, canonical URL, publication time, byline, excerpt, lead image), which is meaningful. It omits any note on freshness/refresh cadence, result count, or ordering, so it is only adequate.

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?

Two short sentences, front-loaded with the action and source, no filler. Minor redundancy in restating 'top stories' three times and in the 'no input needed' clause, which the empty schema already conveys.

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 no-argument, no-output-schema feed tool, the description covers source and return shape well enough to call it correctly. The one real omission is sibling disambiguation against chicagotribune_headlines, which the description should have addressed given how similar the names are.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. 'With no input needed' is a redundant but harmless confirmation of the empty schema.

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 Chicago Tribune top stories') plus the data source ('from its homepage'), which is concrete. However, it never differentiates itself from the sibling chicagotribune_headlines, which on its face sounds like the same content — the agent cannot tell the two apart from the text alone.

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

Usage Guidelines2/5

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

The only usage signal is 'with no input needed', which just restates the empty schema. There is no statement of when to prefer this over chicagotribune_headlines, chicagotribune_article, or chicagotribune_sections, and no exclusions or prerequisites.

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