Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

houston_chronicle_article

Fetch Houston Chronicle article content and metadata from public responses. Flags premium stories using publisher markers without authenticating or bypassing access controls.

Instructions

Get Houston Chronicle article content. Returns public Houston Chronicle article metadata and the body available in the anonymous response. Premium stories are flagged from the publisher's content-tier and JSON-LD markers; the service does not authenticate or bypass access controls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical Houston Chronicle article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does add real value: it discloses that only the anonymous-response body is returned, that premium tiers are flagged via content-tier and JSON-LD markers, and that the service does not authenticate or bypass controls. That sets honest expectations about partial content. It omits error behavior and response shape, keeping it out of the top band.

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?

Three sentences, front-loaded with the core action and then the two caveats (anonymous body, premium flagging). Dense but each sentence carries distinct information; the middle sentence is slightly long but not wasteful.

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 single-URL fetch tool with no output schema and no annotations, the description covers the important unknowns: what content is returned, the paywall limitation, and the no-auth stance. Missing only minor details like failure modes on non-article URLs.

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

Parameters3/5

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

Schema description coverage is 100% and the single url parameter is fully documented as 'Canonical Houston Chronicle article URL'. The description adds nothing about the parameter (e.g. whether canonical/shortened URLs are accepted), so the baseline of 3 applies.

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 article content') and clarifies what is returned (metadata plus the anonymously available body). The sibling tools houston_chronicle_headlines/news/sections are distinct enough by name that no sibling reference is needed, but the description never explicitly contrasts itself with them.

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: this is the fetch-a-single-article tool, so an agent will reach for it when a URL is in hand, and its scope hints that headlines/news tools feed it. However it never states when to use it versus houston_chronicle_news or houston_chronicle_headlines, nor any exclusions.

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