Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rnz_news

Retrieve Radio New Zealand top stories from its all-news feed, including title, article URL, summary, and UTC publication time; no input parameters needed.

Instructions

Get RNZ top stories. Returns RNZ (Radio New Zealand) top stories from its all-news feed: title, article URL, summary and publication time in UTC. Takes no parameters. Lifestyle guides, audio programme pages and section hubs are left out, and article URLs use RNZ's current section names.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/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 reasonably well: it discloses the four returned fields, that times are UTC, that certain page types are filtered out, and how article URLs are formed. It omits any note on refresh cadence, result count, or pagination.

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 tight sentences, front-loaded with the core action, then return shape, then filtering caveats. There is mild redundancy between 'Get RNZ top stories' and 'Returns RNZ top stories'.

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 parameterless news feed with no output schema, the description supplies the field list, timezone and exclusion rules, which is enough to call it correctly. It does not cover result volume or ordering, a minor gap.

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?

Zero parameters, so baseline is 4. The description explicitly confirms 'Takes no parameters', removing any ambiguity for the agent.

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?

Names a specific verb (Get) and resource (RNZ top stories) and describes the feed and its scope, including what is excluded. It does not name or contrast with the closely related siblings rnz_headlines, rnz_sections or rnz_article, so an agent must infer the distinction.

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?

Usage is implied: no parameters, a top-stories feed, and exclusions for lifestyle guides, audio programmes and section hubs. There is no explicit statement of when to pick this over rnz_headlines or rnz_article, which are the obvious alternatives.

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