Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

standard_sections

List Evening Standard RSS sections and slugs accepted by standard-headlines, including names and feed URLs for valid headline categories.

Instructions

Get Evening Standard RSS sections. Lists the Evening Standard sections accepted by standard-headlines, as parent and child slugs such as news, news/london, sport/rugby, going-out/restaurants and homesandproperty/gardening. Each entry has the slug, display name and feed url.

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?

With no annotations, the description carries the burden, and it does so adequately: it declares this is a read/list operation and discloses the returned entry shape (slug, name, url) even without an output schema. It omits pagination/ordering behavior, but for a fixed section list that is negligible.

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 sentences, front-loaded with the purpose, followed by the consuming tool and concrete slug examples. Every sentence earns its place with no filler.

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 zero-arg listing tool with no output schema, the description fully covers what the tool returns (slug, name, url) and how it relates to the sibling it feeds. Nothing an agent needs to invoke or interpret it is missing.

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 takes zero parameters, so the baseline is 4. The description adds meaning by explaining the slug format (parent and child paths) that parameters elsewhere would consume, even though there is no input schema to annotate.

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 Evening Standard RSS sections') and explicitly ties the output to the sibling that consumes it ('accepted by `standard-headlines`'). Examples of parent/child slugs make the resource unambiguous versus the many other `*_sections` tools.

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?

By naming `standard-headlines` as the consumer, it clearly implies when to call this tool (to discover valid section slugs before fetching headlines). It does not spell out explicit when-not conditions, but the context is strong enough for an agent to route correctly.

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