Retrieve fresh headlines from a chosen Indian Express RSS section by passing its section slug. Returns structured JSON headlines for politics, sports, entertainment, and more.
Get The Indian Express section headlines. Returns fresh headlines from one public The Indian Express RSS section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | The Indian Express RSS section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must disclose behavior fully. It states the tool returns 'fresh headlines' from an RSS section, which is useful, but it does not mention limits (e.g., number of headlines, pagination), error handling, or whether the operation is read-only. It is minimal for a tool with no annotation support.
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?
Two sentences with no filler. The main purpose is front-loaded, and the second sentence adds a clarifying detail about freshness and RSS source. Efficient and well-structured.
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?
For a simple one-parameter tool with a well-documented schema, the description is adequate. It states what it returns (headlines) but does not specify the structure (e.g., list of titles, links) or any additional metadata. Given the simplicity, this is sufficient but not rich.
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 schema already describes the sole parameter as 'The Indian Express RSS section slug' and provides a large enum of valid values. The description adds little beyond reiterating 'RSS section'. With 100% schema coverage, the baseline is 3; no additional meaning is needed.
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'), a specific resource ('The Indian Express section headlines'), and clarifies it is from a public RSS section. It is distinct from sibling tools like indianexpress_news or indianexpress_sections, which clearly handle different functions.
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?
The description implies usage: to fetch headlines for a particular section. However, it does not explicitly contrast with alternatives like indianexpress_news or indianexpress_article, leaving the agent to infer when to pick this tool. It provides no exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.