Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thehindu_headlines

Fetch current The Hindu headlines for a chosen section by supplying a required section slug, returning title, URL, summary, author, publication time, and image.

Instructions

Get The Hindu section headlines. Returns the current headlines for one The Hindu section. section is required and takes a slug such as news-national, opinion-editorial, business-markets, sport-cricket or sci-tech-health. Items carry the title, URL, summary, author, publication time and image, and the response echoes the section.

Input Schema

NameRequiredDescriptionDefault
sectionYesThe Hindu 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, the description carries the disclosure burden and does reasonably well: it enumerates the returned item fields (title, URL, summary, author, publication time, image) and notes the response echoes the section. It does not explicitly state that this is a read-only operation or mention rate limits/auth, but the read profile is clearly implied.

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?

Front-loaded with the core action and free of filler overall. The opening two sentences are mildly redundant ('Get... headlines' then 'Returns the current headlines for one... section'), but the return-field list earns its space given there is no output schema.

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-parameter read tool with no output schema, the description compensates by describing the item fields and the echoed section, which is the key missing structured detail. An agent has enough to call it correctly, though it could note the read-only nature explicitly.

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 coverage is 100% and the enum already enumerates every valid slug, so the schema does the heavy lifting. The description adds format confirmation ('takes a slug such as...') with representative examples, but no syntax or semantics the enum doesn't already provide. Baseline 3 is appropriate.

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 ('Get') and resource ('The Hindu section headlines') and scopes it to a single section. This distinguishes it conceptually from thehindu_article/author, but it never names a sibling or clarifies how it differs from thehindu_news or thehindu_sections, so sibling differentiation is left implicit.

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?

Usage is implied: call it to get headlines for one section, with `section` required. It gives example slugs to orient the caller, but there is no explicit when-to-use/when-not guidance relative to thehindu_news or thehindu_sections, leaving the agent to infer the choice.

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