Retrieve the public inventory of News18 RSS sections to use with the headlines endpoint. Get available section names for targeting specific news feeds.
Get News18 RSS sections. Returns the public News18 RSS section inventory used by the headlines endpoint.
| 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?
With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'Get' and the fact that it returns data imply a read-only operation, but it does not explicitly state it is non-destructive, nor does it mention any auth requirements, rate limits, or error behavior. This is minimal but not misleading for a simple retrieval.
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 with no waste. It front-loads the action and includes the essential purpose. It is appropriately sized for a zero-parameter tool.
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?
The description explains what the tool returns and its role relative to the headlines endpoint, which is adequate for a simple inventory fetch. It does not specify the format or whether all sections are included, but with no parameters and no output schema, this is a minor gap and the description is largely complete.
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 the schema is empty. The description does not need to explain parameters, and the baseline for 0 params is 4. It does not add parameter-specific detail because there is nothing to add.
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 clearly states the action (Get), the resource (News18 RSS sections), and the purpose (returns the section inventory used by the headlines endpoint). It distinguishes from siblings like news18_article and news18_headlines by specifying this is the section inventory, and the name disambiguates from other sources' sections tools.
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 by noting it is the inventory used by the headlines endpoint, suggesting it should be used when you need to know the available News18 sections. However, it does not explicitly mention alternatives or when not to use it, leaving the agent to infer the appropriate context from the name and sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.