Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rte_headlines

Get RTÉ News section headlines by slug; returns title, URL, summary, publication time, and image for each story.

Instructions

Get RTÉ News section headlines. Returns the latest RTÉ News stories for one section. section is required and takes one of 29 slugs such as ireland, world, politics, dublin, courts or nuacht (Irish-language); others return a 400. Each item has its title, URL, summary, publication time and image. Small sections like science return only a handful of items.

Input Schema

NameRequiredDescriptionDefault
sectionYesRTÉ News section slug

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 well: it discloses the 400 error for invalid slugs, the shape of each returned item (title, URL, summary, publication time, image), and that small sections like 'science' return only a handful of items. No auth or rate-limit context, but behavioral coverage is solid.

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?

Purpose is front-loaded in the first sentence, followed by return shape and edge-case notes. Four sentences, each earning its place, though the 'section is required' restatement is slightly redundant with the schema.

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 tool with no output schema and no annotations, the description covers purpose, parameter values, error behavior, and return fields. An agent has what it needs to call it correctly; only cross-tool routing is unaddressed.

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% so baseline is 3, but the description adds real value beyond the enum: concrete slug examples, the note that 'nuacht' is Irish-language, and the 400 failure mode for out-of-enum values.

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 RTÉ News section headlines') and clarifies scope ('the latest RTÉ News stories for one section'). It does not explicitly distinguish itself from siblings like rte_news or rte_sections, which is the only gap.

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?

Implied usage is clear from 'for one section', and the description warns that non-listed slugs return a 400. However, it never says when to prefer this over rte_sections (to discover slugs) or rte_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