Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

birminghammail_sections

List Birmingham Mail sections, including slugs, names, and feed URLs, so you can choose valid categories for headline queries; only recently updated feeds are included.

Instructions

Get Birmingham Mail sections. Lists the 23 Birmingham Mail sections that birminghammail-headlines accepts, such as news/midlands-news, black-country, sport/football/transfer-news and whats-on. Each has a slug, a display name and the feed url. Only sections with a recently updated feed are included (last verified 2026-09-25), and each returns up to about 25 entries.

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 disclosure burden and does well: it names the returned fields (slug, name, url), discloses the freshness filter (only recently updated feeds, verified 2026-09-25) and the ~25-entry cap per section. It does not mention auth, rate limits, or pagination/caching behavior, so it is not exhaustive.

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 short sentences, front-loaded with the core purpose, then scope, then the sibling/format linkage. Every sentence adds distinct information with no repetition of the title or schema.

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?

With no output schema, no parameters, and no annotations, the description compensates fully by describing return fields, example slugs, the freshness constraint, and the item cap. Nothing needed to call this zero-argument tool correctly 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; there is nothing for the description to clarify. It helpfully describes the shape of the returned objects instead, which is the only semantic gap a caller could have.

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 Birmingham Mail sections'), quantifies scope (23 sections), and explicitly ties the output to the sibling tool birminghammail-headlines. An agent can distinguish it from birminghammail_headlines/news/article siblings 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?

The description makes the use case clear implicitly: these are the sections that `birminghammail-headlines` accepts, so this is the discovery step before fetching headlines for a section. It never states an explicit 'use this when / not when' rule, but the routing intent is unambiguous.

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