Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

liverpoolecho_sections

Lists Liverpool Echo sections accepted by the headlines tool, with slugs, display names, and feed URLs to help you target valid news, sport, and local feeds.

Instructions

Get Liverpool Echo sections. Lists the Liverpool Echo sections accepted by liverpoolecho-headlines, such as news/liverpool-news, sport/football/transfer-news, whats-on/theatre-news and in-your-area. Each entry has a slug, display name and feed url. Each listed section had at least one current entry when last checked, and feeds hold up to about 25 entries.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/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 and mostly succeeds: it discloses the entry fields (slug, name, url), a freshness guarantee ('at least one current entry when last checked'), and a capacity bound ('up to about 25 entries'). It does not cover pagination or caching, which is the remaining 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?

Four short sentences, front-loaded with the purpose, then examples, return fields, and freshness/size caveats. No filler; every sentence adds usable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must describe return values, and it does (slug/name/url plus size and freshness constraints). Missing only pagination/ordering behavior, which is minor for a small static list.

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 goes beyond by explaining the semantics of the returned slug values and their relationship to the headlines tool, though this is output-facing rather than parameter documentation.

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+resource ('Get Liverpool Echo sections') and immediately disambiguates from its many `*_sections` siblings by tying the output to `liverpoolecho-headlines`. Concrete example slugs make the payload's shape unambiguous.

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 phrase 'sections accepted by `liverpoolecho-headlines`' effectively tells the agent when to reach for this tool (discovering valid section slugs before querying headlines). It stops short of stating exclusions or naming a sibling to avoid, so it is clear context but not full when/when-not guidance.

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