Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

theblaze_article

Fetch a Blaze Media article from a canonical theblaze.com URL, returning title, authors, dates, image, paragraphs, and a paywall flag; reject non-editorial or off-site links.

Instructions

Get a Blaze Media article. Returns one TheBlaze (Blaze Media) article by url, a canonical HTTPS editorial or show-story link on theblaze.com; non-editorial paths and off-site URLs are rejected. The response has the title, description, section, authors, publication and update times, image URL, body paragraphs and a paywalled flag.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical theblaze.com article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4/5.0
Behavior4/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 discloses URL validation rules (canonical HTTPS editorial or show-story link; non-editorial and off-site URLs rejected) and describes the return payload including a paywalled flag. It does not cover error behavior, but the transparency is strong for a simple read tool.

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?

Front-loaded with the tool's purpose, then tightly packs URL constraints and return fields into two additional sentences. No wasted words and every sentence adds useful information.

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

Completeness5/5

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

For a single-parameter lookup with no output schema, the description fully explains accepted inputs and the shape of the returned article, including the paywalled flag. Nothing essential is missing for correct invocation.

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?

Schema description coverage is 100% for the single URL parameter, but the description adds meaningful constraints beyond the schema: the URL must be a canonical HTTPS editorial or show-story link on theblaze.com, and non-editorial paths or off-site URLs are rejected. This supplements the terse schema annotation.

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 ('Get') and resource ('a Blaze Media article') and clarifies it returns exactly one article by URL. It does not explicitly distinguish itself from sibling tools like theblaze_headlines or theblaze_news, but the scope is otherwise clear.

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: you must supply a canonical URL to fetch an article. It does not state when to use this tool versus alternatives such as theblaze_news or theblaze_headlines, nor does it name any alternatives explicitly.

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