Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

rte_sections

Lists the 29 RTÉ News section hubs with slug, display name, and feed URL so you can find valid section identifiers to use in headline requests.

Instructions

Get RTÉ News sections. Lists the 29 RTÉ News section hubs that rte-headlines accepts, such as ireland, politics, dublin, ukraine and investigations-unit. Each entry has a slug, a display name and the feed url. The list is curated to hubs with their own article feed, so narrower topic pages are not included.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.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 burden and does a good job: it discloses that each entry has a slug, name, and feed URL, and that the list is curated to hubs with their own article feed. It does not discuss auth or rate limits, but those are not central for this simple listing tool.

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?

Three efficient sentences, front-loaded with the purpose and then the return shape and curation rule. Every sentence adds useful information with no repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter listing tool with no output schema and no annotations, the description is complete: it explains what is returned, the fields, and the curation boundary excluding narrower topic pages.

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?

The tool has zero parameters, so there is no parameter semantics to explain. The baseline for a zero-parameter tool is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 sections") and explains that it lists the 29 section hubs accepted by rte-headlines. The examples and return fields make the tool clearly distinguishable from rte_headlines and rte_news.

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

Usage Guidelines4/5

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

Explicitly connects the tool to rte-headlines by saying it lists the section hubs that rte-headlines accepts, which tells an agent how this list is used. It does not spell out exclusions or alternatives beyond that, but the primary usage context is clear.

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