Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

national_headlines

Fetch current The National headlines by editorial section slug, returning structured stories or an empty list when no items exist.

Instructions

Get The National section headlines. Returns current The National stories from a public Arc category RSS feed. Pass one of the editorial section slugs from national_sections. A valid category with no current stories returns an empty items list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sectionYesThe National editorial section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A3.6/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 does disclose meaningful traits: the feed is public RSS (implying no auth) and a valid category with no current stories returns an empty items list. However, it omits rate limits, result counts/pagination, and caching behavior, leaving notable gaps for a no-annotation tool.

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 compact sentences with no filler; the purpose is front-loaded, followed by data source and the empty-result edge case. Slight redundancy between the name and the opening sentence keeps it short of a 5.

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 single-parameter, no-output-schema, no-annotation tool, the description covers input provenance and the empty-list edge case, which is enough to invoke it correctly. It could mention what a returned item contains, but that gap is minor.

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% and the enum of 58 slugs already constrains the parameter, so the baseline is 3. The description adds real value by telling the agent the slugs must be sourced from the sibling national_sections tool, which the schema does not convey.

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+resource ('Get The National section headlines') and names the data source ('public Arc category RSS feed'), so an agent knows it returns headline items rather than article bodies or author profiles. It does not explicitly distinguish itself from the sibling national_news, which slightly limits differentiation.

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 tells the agent where valid input values come from ('one of the editorial section slugs from national_sections'), which is useful routing guidance, but it never says when to pick this tool over national_news or national_article, and gives no exclusions or prerequisites.

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