Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

independent_news

Fetches The Independent's current news stories, returning titles, URLs, summaries, authors, publication times, image URLs, and types; no parameters needed.

Instructions

Get The Independent top stories. Returns the current top stories from The Independent. It takes no parameters. Each item has its title, URL and, where the outlet gives them, a summary, author, publication time, image URL and type. Use the headlines endpoint for one section.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool takes no parameters and describes the returned item fields, including optional fields that appear only 'where the outlet gives them'; it does not cover pagination, rate limits, or auth, but for a public top-stories endpoint this is still 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?

The description is front-loaded and mostly tight, but the first two sentences are redundant: 'Get The Independent top stories' and 'Returns the current top stories from The Independent' say nearly the same thing. The alternative routing sentence earns its place.

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?

With no output schema and no annotations, the description must be self-contained. It covers purpose, no-parameter behavior, return item shape, and the alternative for section-specific requests, which is complete for a simple read-only top-stories endpoint.

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?

There are zero parameters and the schema is empty. The description explicitly states 'It takes no parameters,' matching the schema, so the baseline of 4 for a no-parameter tool applies.

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 top stories from The Independent. It also distinguishes the tool from the sibling headlines endpoint by noting that headlines is for one section.

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

Usage Guidelines5/5

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

Explicitly routes section-specific requests to the headlines endpoint, implying this tool is for current top stories across sections. The alternative and the condition selecting it are both named.

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