Retrieve top Hindustan Times stories from its public feed. Returns structured JSON for news integration.
Get Hindustan Times top stories. Returns fresh Hindustan Times top stories from its public "Latest News" feed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that results are 'fresh' and come from a 'public' feed, which implies a read-only, unauthenticated operation. However, it does not describe the return format, story count, or any pagination/rate-limit behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loads the action, but it repeats 'Hindustan Times top stories' in both sentences. It earns its place overall, with only mild redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters, no output schema, and no annotations, the description is the sole source of information. It covers the core purpose but omits what the returned stories look like (fields, structure, count) and any limitations, which is a notable gap for an agent deciding whether this tool's output will satisfy a request.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and an empty input schema, so there is nothing for the description to explain about parameters. The baseline of 4 applies when no parameters exist.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Get') and resource ('Hindustan Times top stories'), and adds the source ('public Latest News feed'). It makes clear this tool returns a news feed, though it does not explicitly distinguish itself from the closely related sibling 'hindustantimes_headlines'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance or alternatives are mentioned. Given the large sibling list with hindustantimes_headlines, hindustantimes_article, hindustantimes_sections, an agent is left to infer when to select this tool over the others. It only implies use for top/latest stories.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.