Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

men_sections

Lists Manchester Evening News sections accepted by men-headlines, returning stable slugs, display names, and URLs for filtering headlines.

Instructions

Get Manchester Evening News sections. Lists the Manchester Evening News sections accepted by men-headlines, such as news, news/uk-news, sport/football, whats-on/music-nightlife-news and trips-and-breaks. Each entry has a stable slug, display name and section url. Takes no parameters.

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 load and does reasonably well: it declares the tool takes no parameters and describes the shape of each entry (stable `slug`, display `name`, section `url`). It omits anything about auth, caching, or ordering, but for a simple read-only enumeration that is a minor gap.

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 tight sentences, front-loaded with the purpose, then the consumer relationship, then the return shape. No filler and nothing that restates the tool name.

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?

There is no output schema, so the description must, and does, describe the returned fields. For a 0-param read-only enumeration that routes an agent into `men-headlines`, nothing further is required to call it correctly.

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 schema surface to explain; the explicit statement 'Takes no parameters' removes any ambiguity about how to invoke it. Baseline for a 0-param tool, with a small credit for stating it outright.

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 Manchester Evening News sections') and immediately scopes it by naming the consumer tool, `men-headlines`. The concrete slug examples (`news/uk-news`, `sport/football`) make it unmistakable against siblings like men_news, men_headlines, and men_article.

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 discloses the operative context: these are the sections accepted by `men-headlines`, so an agent knows to call this first and feed a slug into the headlines tool. It does not name explicit alternatives or when-not to use it, so it falls short of a full when/when-not statement.

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