Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

dailyexpress_sections

Lists available Daily Express sections, such as news, uk, royal, sport, and personal-finance, so callers can choose valid section slugs for headline queries.

Instructions

Get Daily Express sections. Lists the Daily Express sections that dailyexpress-headlines accepts, such as news, uk, royal, sport and personal-finance. Each entry has a stable slug, a display name and the 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?

No annotations are supplied, so the description carries the full burden; it discloses that the tool takes no parameters and that each result carries a stable `slug`, display `name` and `url`, which is useful return-shape information given the absence of an output schema. It does not cover safety/rate-limit properties, though those are low-risk for a read-only listing.

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, followed by concrete example slugs and the return shape. No filler or repetition, and the routing information is placed prominently.

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 no-parameter listing with no output schema or annotations, the description covers what the tool returns (slug/name/url), why it matters (feeds `dailyexpress-headlines`), and that no inputs are needed—everything an agent needs to invoke 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, which sets a baseline of 4, and the description explicitly confirms 'Takes no parameters.' There are no parameter semantics to elaborate beyond that.

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 ('Daily Express sections'), and explicitly ties the result to the sibling `dailyexpress-headlines`, which it says consumes these slugs. An agent can immediately distinguish this reference-style lookup from article/news 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?

Provides clear context by identifying the consumer of the slugs (`dailyexpress-headlines`), implying the tool should be called to discover valid section values before requesting headlines. It does not spell out when not to use it or name alternative section-based tools, so it lacks explicit exclusions or alternatives.

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