Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

thehindu_news

Fetch The Hindu's top stories as structured items with title, URL, summary, author, publication time, and image URL. For a single desk like cricket or business, use the headlines endpoint.

Instructions

Get The Hindu top stories. Returns the current stories from The Hindu's Latest News listing. It takes no parameters. Each item has its title, URL and, where available, a summary, author, publication time, image URL and type. For a single desk such as cricket or business, use the headlines endpoint.

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 useful work: it states the tool takes no parameters and discloses the return shape (title, URL, summary, author, publication time, image URL, type). It omits freshness/rate-limit/auth context, but for a public news getter 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 front-loaded sentences that each add information. 'Get The Hindu top stories' and 'Returns the current stories from The Hindu's Latest News listing' overlap slightly, but the second sentence pins the exact source.

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?

With no output schema, the description must describe return values, and it lists the fields returned including the conditional summary/author/time/image/type. Nothing essential for a zero-parameter feed lookup is missing.

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, so the baseline is 4. The description confirms 'it takes no parameters', consistent with the empty schema, and adds nothing misleading.

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?

Specific verb 'Get' plus resource 'The Hindu top stories', anchored to 'The Hindu's Latest News listing' so the source is unambiguous. It clearly differs from the sibling thehindu_headlines by scope.

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?

Explicitly routes the agent to an alternative: 'For a single desk such as cricket or business, use the headlines endpoint.' That gives a clear condition selecting a sibling, though it does not cover other alternatives or when-not-to-use cases.

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