Fetch Blaze Media section headlines from public RSS feeds; specify a section slug to retrieve current articles for that category.
Get Blaze Media section headlines. Returns headlines from a public section RSS feed. Use /theblaze/sections to discover the complete accepted section list.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Exact Blaze Media section slug |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It discloses that the data comes from a public RSS feed, implying read-only and low-risk behavior, but says nothing about freshness, result limits, or return shape. Adequate but thin for a feed tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the purpose, then the source, then the discovery instruction. No filler; every sentence carries information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter, no-output-schema tool, the description covers purpose, source, and how to obtain valid section values. Minor gaps around result format and volume, but nothing an agent needs in order to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a 45-value enum and a description of 'Exact Blaze Media section slug'. The description reinforces this via the sections-discovery pointer but adds no format or syntax detail beyond the schema. Baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
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 section headlines) and identifies the data source as a public section RSS feed. It distinguishes itself reasonably from siblings like theblaze_news and theblaze_article, though it does so implicitly rather than naming them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent to theblaze_sections to discover the accepted section list, which is the key usage prerequisite for this tool. It gives no explicit when-not guidance, but the discovery pointer covers the main risk of misuse.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.