Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

walesonline_headlines

Fetch up to 25 recent WalesOnline headlines for a specific section using a valid slug, such as news/politics or sport/rugby; invalid slugs return a 400 error.

Instructions

Get WalesOnline section headlines. Lists recent WalesOnline headlines for one section, up to about 25 items. section is required and takes a slug such as news/wales-news, news/politics, sport/rugby, sport/football or whats-on; walesonline-sections lists all 37. Photo galleries are omitted, and an invalid value returns a 400 error.

Input Schema

NameRequiredDescriptionDefault
sectionYesWalesOnline section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/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 disclose useful traits: a result cap ('up to about 25 items'), content filtering ('photo galleries are omitted'), and error behavior ('invalid value returns a 400 error'). It omits auth or rate-limit details, but the operational behavior is well covered.

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?

Purpose is front-loaded, followed by result count, parameter guidance, and edge cases. Every clause adds actionable information with no filler.

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 list tool with no output schema, the description covers what is returned (headlines, ~25 max), filtering, and error behavior. Minor gap: it doesn't describe the shape of a returned item, though this is a lightweight list tool.

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 adds value by giving example slugs and pointing to walesonline-sections to enumerate all 37 sections, plus restating that the parameter is required.

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 (Get/Lists) and resource (WalesOnline section headlines) with scope ('for one section'). It also names the sibling walesonline-sections, letting an agent distinguish it without opening any schema.

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?

Tells the agent it lists headlines for a single section and routes to walesonline-sections to discover valid slugs. It gives clear context but doesn't contrast against other WalesOnline siblings like walesonline_news or walesonline_article.

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