Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nbc_headlines

Fetch NBC News headlines for a chosen section such as politics, business, or health. Get recent story titles, URLs, summaries, and publication times as structured JSON.

Instructions

Get NBC News section headlines. Returns recent NBC News stories for one section. section is required and must be one of news, world, us-news, politics, business, science or health. Each item has a title and URL, and may include summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesNBC News RSS section slug: news, world, us-news, politics, business, science, or health

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 usefully discloses the return shape (title, URL, optional summary, author, publication time, image) and that stories are 'recent', which compensates for the missing output schema. It still omits operational details like result limits or update frequency.

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 purpose, then return shape, then parameter rules. The enum list is repeated from the schema, which is slightly redundant, but overall it is efficient and well-structured.

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 simple section-headlines tool with no output schema, the description covers purpose, required parameter, allowed values, and return fields. It stops short of describing result count or freshness guarantees, but it is largely complete for correct invocation.

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 enum is fully documented in the schema. The description repeats the required parameter and allowed values, adding no meaning beyond what the structured data already provides, 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 ('Get') and resource ('NBC News section headlines') and scopes it to one section. It is clear what the tool returns, but it does not name or differentiate from sibling tools like nbc_news, nbc_sections, or nbc_author, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as nbc_news or nbc_sections. The description only says what it does, not when or when not to choose it.

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