Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

independent_headlines

Fetch current The Independent headlines for one of 17 sections by slug, returning titles, URLs, summaries, authors, and publication times.

Instructions

Get The Independent section headlines. Returns the current headlines for one The Independent section. section is required and takes one of 17 slugs, such as news/uk, news/world, sport, voices, money or bulletin. Each item has its title and URL, plus summary, author, publication time and image when the outlet provides them, and the response echoes the section.

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Independent RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden and does reasonably well: it discloses the return shape (title, URL, optional summary, author, publication time, image) and that the response echoes the section. It does not mention rate limits, auth, or result-count behavior, but for a read-only headline fetch this is solid disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core purpose and resource, then parameter constraint, then return shape. Every sentence contributes; no filler padding.

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?

There is no output schema, so the description's enumeration of returned fields and the optional-field caveat ('when the outlet provides them') is genuinely useful and fills that gap. Complete enough for a single-parameter headline endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the enum already lists all 17 slugs, so the schema does the heavy lifting. The description adds the count ('17 slugs') and repeats example slugs, adding only marginal meaning beyond the structured field. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Get The Independent section headlines' and 'Returns the current headlines for one The Independent section.' An agent can tell it is a headline-fetching tool, though it never explicitly distinguishes itself from close siblings like independent_news or independent_sections.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It notes that `section` is required and enumerates representative slugs, which implies the calling pattern, but it offers no when-to-use guidance and names no alternative tool (e.g., independent_news or independent_article) that might be preferred in other situations.

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