Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indianexpress_news

Fetch current top stories from The Indian Express, including titles, URLs, summaries, authors, publication times, and images. Use the headlines endpoint to read a single section.

Instructions

Get The Indian Express top stories. Returns the current top stories from The Indian Express. 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 to read one section.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 disclose that it takes no parameters and enumerates what each item contains (title, URL, and optionally summary, author, publication time, image URL, type), including the variability of optional fields. It omits freshness/update cadence and any upstream constraints, leaving some behavioral gaps.

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?

Purpose is front-loaded and the alternative is placed last, which is reasonable ordering. The second sentence ('Returns the current top stories...') largely restates the first, adding only the 'current' freshness nuance, so there is minor redundancy but no bloat.

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 correctly explains the return shape and optional fields, and it clarifies the no-parameter contract. For a simple read-only top-stories endpoint this is nearly complete, missing only update frequency and any paging/limit behavior.

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 is the baseline-4 case. The description reinforces this by stating 'It takes no parameters,' so nothing is left ambiguous.

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 Indian Express top stories') and scopes it as cross-paper top stories with no filtering. It explicitly distinguishes itself from the sibling 'headlines' endpoint, which reads one section, so an agent can route between the two without opening either schema.

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 an explicit alternative: 'Use the headlines endpoint to read one section,' implying news is for the top-stories overview. It gives clear context but does not address the other siblings (indianexpress_article, indianexpress_author, indianexpress_sections), so routing guidance is partial rather than exhaustive.

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