Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rnz_headlines

Fetch current Radio New Zealand headlines by required section slug to retrieve story titles, URLs, summaries, and publication times for news monitoring or research.

Instructions

Get RNZ section headlines. Returns the latest RNZ (Radio New Zealand) stories for one section. section is required and takes one of 19 slugs such as news, national, political, business, pacific, te-manu-korihi or weather; others return a 400. Each item has its title, URL, summary and publication time. Smaller sections can carry items from earlier weeks, so check published_at.

Input Schema

NameRequiredDescriptionDefault
sectionYesRNZ section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does add real behavior: invalid slugs return a 400, each item exposes title/URL/summary/published_at, and smaller sections can return stale earlier-week items. It omits auth, rate limits, and pagination, so it stops short of full disclosure.

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?

Five tight sentences, front-loaded with purpose, then the required parameter, then the shape of the returned items, then the freshness caveat. Nothing is redundant and the most important constraint (required enum) comes early.

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-enum-parameter tool with no output schema, the description covers input constraints, error behavior, and the returned fields plus a freshness warning. Only auth/rate-limit/pagination context is absent, which is minor at this complexity.

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 coverage is 100% with an enum, so the baseline is 3. The description goes beyond the raw enum by giving representative slugs, confirming 19 valid values, and specifying that any other value produces a 400 — meaningful semantics 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 and resource ("Get RNZ section headlines ... latest RNZ stories for one section"), which is clear enough to separate it from single-article tools like rnz_article. However, it never names or contrasts any sibling (rnz_news, rnz_sections), so the differentiation is inferred rather than explicit.

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?

It establishes that `section` is required and which values are valid, which implies the usage context. But it gives no explicit when-to-use guidance or alternatives (e.g., why choose this vs rnz_news), leaving routing to inference.

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