Skip to main content
Glama

theblaze_headlines

Read-only

Fetch current TheBlaze article headlines and URLs from one verified section feed; provide a slug from theblaze_sections.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "section": "<section>"
    },
    "name": "theblaze_headlines"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesExact Blaze Media section slug. Documented values: news, columns, columns/opinion, columns/analysis, tech, lifestyle, lifestyle/men, lifestyle/women, lifestyle/provisions, fearless, exclusive, original, politics, your-opinion, shows, shows/back-to-the-people, shows/blaze-news-tonight, shows/blaze-originals, shows/blazetv-specials, shows/come-take-it-with-sara-gonzales, shows/conservative-review-with-daniel-horowitz, shows/dusty-bluffs, shows/fearless-with-jason-whitlock, shows/glenn-tv, shows/kibbe-on-liberty, shows/live-free-with-josh-howerton, shows/making-the-argument-with-nick-freitas, shows/pat-gray-unleashed, shows/relatable, shows/rufo-lomez, shows/sara-gonzales-unfiltered, shows/steve-deace-show, shows/strange-encounters, shows/stu-and-dave-do-america, shows/the-auron-macintyre-show, shows/the-coverup, shows/glenn-beck-podcast, shows/the-glenn-beck-program, shows/the-john-doyle-show, shows/the-liz-wheeler-show, shows/the-rick-burgess-show, shows/zero-hour, contributors, jan-6-truth.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / section / description
      Added value: +"Exact Blaze Media section slug. Documented values: news, columns, columns/opinion, columns/analysis, tech, lifestyle, lifestyle/men, lifestyle/women, lifestyle/provisions, fearless, exclusive, original, politics, your-opinion, shows, shows/back-to-the-people, shows/blaze-news-tonight, shows/blaze-originals, shows/blazetv-specials, shows/come-take-it-with-sara-gonzales, shows/conservative-review-with-daniel-horowitz, shows/dusty-bluffs, shows/fearless-with-jason-whitlock, shows/glenn-tv, shows/kibbe-on-liberty, shows/live-free-with-josh-howerton, shows/making-the-argument-with-nick-freitas, shows/pat-gray-unleashed, shows/relatable, shows/rufo-lomez, shows/sara-gonzales-unfiltered, shows/steve-deace-show, shows/strange-encounters, shows/stu-and-dave-do-america, shows/the-auron-macintyre-show, shows/the-coverup, shows/glenn-beck-podcast, shows/the-glenn-beck-program, shows/the-john-doyle-show, shows/the-liz-wheeler-show, shows/the-rick-burgess-show, shows/zero-hour, contributors, jan-6-truth."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-fetch behavior are covered. The description adds only that results are 'current' and drawn from 'one verified section feed' (one section per call), which is useful but modest beyond the annotations.

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?

A single, front-loaded sentence pairs the action with the scoping constraint and the parameter prerequisite; nothing is wasted.

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?

With an output schema present, return values need no explanation, and the description covers purpose and parameter sourcing. It is nearly complete; only a note on behavior for invalid/empty sections would round it out.

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 'section' parameter already enumerates all documented slugs, so the schema does the heavy lifting. The description adds the sourcing hint ('from theblaze_sections') but no format or error-handling detail beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Fetch), resource (TheBlaze article headlines and URLs), and scope (one verified section feed). It also points at theblaze_sections as the source of valid slugs, so an agent can distinguish it from theblaze_article/news without opening a schema.

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

Usage Guidelines4/5

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

Gives a concrete prerequisite: the section argument must be a slug obtained from theblaze_sections, and constrains the call to a single feed. It does not, however, state when to prefer this over siblings like theblaze_news or theblaze_article.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.