Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indianexpress_headlines

Fetch current The Indian Express headlines for a chosen section slug, returning titles, URLs, summaries, authors, publication times, and images.

Instructions

Get The Indian Express section headlines. Returns the current headlines for one The Indian Express section. section is required and takes a slug such as india, explained, cities-delhi, entertainment-bollywood, sports-cricket or political-pulse. Items carry title, URL, summary, author, publication time and image, and the response echoes the section.

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Indian Express RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose freshness ('current headlines') and the returned item fields (title, URL, summary, author, publication time, image), which is useful, but says nothing about read-only nature, rate limits, result count, or pagination — notable gaps for a tool with zero annotation coverage.

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 action, and no filler. However the opening two sentences restate each other ('Get ... section headlines' then 'Returns the current headlines for one ... section'), a small amount of redundancy.

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 single-required-param tool with full schema coverage and no output schema, the description is largely sufficient; enumerating the returned item fields usefully substitutes for a missing output schema. Only freshness guarantees and result volume are unaddressed.

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 enumerates every valid slug, so the schema does the heavy lifting and a 3 baseline applies. The description's example slugs and the note that the response echoes `section` add marginal value but no syntax beyond what the enum provides.

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?

States a specific verb and resource ('Get The Indian Express section headlines') scoped to a single section, which implicitly distinguishes it from a multi-section wire like indianexpress_news. It never names a sibling or clarifies its relationship to indianexpress_sections or indianexpress_article, so the differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, prerequisites, or alternatives. It implies the tool fetches one section's headlines but never says when to pick it over indianexpress_news or indianexpress_article, leaving routing entirely to inference.

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