Fetch section or city-edition headlines from The Times of India by slug. Get clean headline lists for top stories, business, sports, tech, and more.
Get The Times of India section headlines. Returns fresh headlines from one public Times of India section or city-edition feed.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Times of India section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the behavioral burden. It adds the context that the feed is 'public' and 'fresh', implying a read-only operation without authentication, but it does not disclose output format, pagination, rate limits, or whether only headline text is returned.
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 two sentences and front-loads the core action. It is appropriately concise, though 'headlines' appears in both sentences, creating slight redundancy that does not add much extra value.
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?
Given the tool's simplicity (one enum parameter, no output schema), the description covers the basic selection and purpose. However, without an output schema, the description should clarify what the returned 'headlines' look like (plain strings, objects with links, etc.), which is a notable gap for an agent invoking the tool.
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?
Schema description coverage is 100%, and the enum lists all valid section slugs. The description adds only marginal meaning by noting the feed is 'public' and includes 'city-edition', which hints that the section parameter covers city slugs, but it largely repeats what the schema already conveys.
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 uses a specific verb and resource: 'Get The Times of India section headlines' and further scopes it to 'one public Times of India section or city-edition feed.' This clearly conveys what the tool does, though it does not explicitly name sibling tools such as timesofindia_news or timesofindia_sections to differentiate them.
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?
There is no guidance on when to use this tool over alternatives. The description implies it is for section-level headlines, but it does not mention exclusions or point to sibling tools like timesofindia_news for full news items or timesofindia_sections for listing sections.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.