Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

houston_chronicle_sections

Retrieve live-verified public editorial sections from the Houston Chronicle headlines endpoint, excluding newsletters, games, audio-only, marketplace, and interactive links.

Instructions

Get Houston Chronicle sections. Returns every live-verified public editorial section accepted by the Houston Chronicle headlines endpoint. Newsletter, games, audio-only, external marketplace and interactive project/tool links are excluded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses what is returned (live-verified public editorial sections) and what is filtered out (newsletter, games, audio-only, marketplace, interactive project/tool links), but never states read-only/safety semantics, result count, ordering, or pagination for a listing operation.

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

Conciseness5/5

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

Two sentences, no waste, and the return scope is front-loaded ahead of the exclusion list. Every clause earns its place by defining what qualifies as a section.

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-parameter list tool with no annotations and no output schema, the description covers what is returned and, importantly, what is excluded. It stops short of describing ordering, count, or how to chain into the headlines tool, which are minor for such a simple lookup.

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 and the schema is empty, so there is nothing to document; the baseline for a parameterless tool applies. The description correctly adds no spurious parameter claims.

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 Houston Chronicle sections) and immediately scopes it to what the headlines endpoint accepts, which is more than a bare name restatement. It distinguishes itself from the many sibling *_sections tools by naming the source publication, but does not explicitly contrast with houston_chronicle_headlines or houston_chronicle_news.

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 implied rather than stated: the section list is tied to the headlines endpoint and exclusion of newsletters/games/audio implies a clean editorial-topic enumeration. There is no explicit 'use this when... use X instead' routing against the sibling headlines/news/article tools.

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