Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

independent_sections

Lists the 17 The Independent RSS section slugs accepted by the headlines endpoint, including news, UK, lifestyle, voices, money, and bulletin, each with slug, name, and URL.

Instructions

Get The Independent RSS sections. Lists the 17 The Independent section slugs that the headlines endpoint accepts, from news and news/uk to life-style, voices, money and bulletin. Each entry has a slug, a display name and a url.

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 burden and does reasonably well: it discloses the exact count (17), the return shape (each entry has `slug`, display `name`, `url`), and sample values. It does not state read-only nature or format explicitly, but for a zero-param listing endpoint the behavioral picture is largely complete.

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 verb and resource, then the count and accepted slugs, then the return shape. No filler and every sentence carries 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?

For a zero-param, no-output-schema listing tool, the description covers what it returns and why it matters. It could be marginally stronger by explicitly naming the consumer tool, but nothing an agent needs to call it 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 schema baseline of 4 applies. There is nothing further for the description to document on the input side.

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 The Independent RSS sections') and pins down scope precisely: the 17 section slugs accepted by the headlines endpoint, with concrete examples ranging from `news`/`news/uk` to `life-style`, `voices`, `money`, `bulletin`. An agent can immediately tell this apart from sibling article/headlines 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?

By naming 'the headlines endpoint accepts', it implies the correct downstream use of the returned slugs. However, it never explicitly names the sibling tool (e.g. independent_headlines) or states the when-not condition, leaving the routing to inference rather than making it explicit.

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