Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

theblaze_news

Fetch Blaze Media stories for current news and opinion coverage. Returns up to 30 site-wide items with headline, URL, publication time, byline, summary, and image.

Instructions

Get Blaze Media top stories. Returns the latest site-wide stories from TheBlaze (Blaze Media), up to 30 items, covering news and opinion. Each item has a headline, canonical URL, publication time, byline, summary and image URL when published. It takes no parameters.

Input 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 behavioral burden. It usefully discloses the maximum of 30 items and the fields returned, and 'Get' implies a read-only operation, but it does not mention authentication, rate limits, ordering guarantees, or pagination behavior.

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?

The description is three sentences, front-loads the purpose, and then adds only useful return-shape details. There is no filler or redundant restatement of the tool name.

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-parameter, no-output-schema news feed tool, the description is nearly complete: it names the source, scope, item cap, and returned fields. A minor gap is that it does not clarify ordering or pagination beyond saying 'latest.'

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, which is the baseline for a 4. The description also explicitly says 'It takes no parameters,' matching the empty schema and leaving no ambiguity.

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 Blaze Media top stories' and clarifies that it returns latest site-wide stories from TheBlaze covering news and opinion. It is clear what the tool does, though it does not explicitly distinguish itself from the sibling theblaze_headlines tool.

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?

The description implies usage by calling these 'top stories' and 'latest site-wide stories,' so an agent can infer it is for fetching recent Blaze Media news. However, it does not state when to choose this over theblaze_headlines, theblaze_article, or theblaze_sections.

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