Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metro_sections

List Metro section slugs with display names and URLs to choose valid categories for metro-headlines queries.

Instructions

Get Metro sections. Lists the 42 Metro section slugs accepted by metro-headlines, each with its display name and URL. Slugs include uk, football, showbiz and coronation-street. home is the site-wide stream, the same stories as metro-news, and parent sections such as news and sport aggregate their child sections.

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 full burden. It clearly implies a read-only listing operation, states the number of returned sections and the fields returned, and explains how special section types behave.

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?

The definition is front-loaded with the core purpose, then adds only useful details: count, field shape, example slugs, and special-case behavior. Every sentence earns its place without redundancy.

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 simple zero-parameter listing tool with no output schema and no annotations, the description is complete enough. It explains what is returned, how many items, and how key slugs relate to sibling tools, leaving no critical gap for correct invocation.

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 no parameters, so the baseline is 4 under the rubric. The description correctly does not introduce parameter semantics that do not exist.

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?

The description states a specific verb and resource: it lists the 42 Metro section slugs with display name and URL. It explicitly connects the output to `metro-headlines`, distinguishing it from sibling tools like `metro_news` and `metro_headlines`.

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?

It clearly implies the tool is used to discover valid slugs before calling `metro-headlines`, and it explains special cases such as `home` matching `metro-news` and parent sections aggregating children. It does not explicitly state when not to use the tool, but the context is strong.

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