Latest source-backed news from the Asha News archive. Returns items with publish time, source, and citation links.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Keyword to search within recent coverage. | |
| limit | No | Max items (default 10). | |
| category | No | Canonical category filter: world, politics, markets, tech, ai, science, health, sport, or entertainment. | |
| timeframe | No | e.g. 24h, 72h. Default 24h. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description adds the return format and the 'source-backed' nature of the news. However, it does not disclose filtering capabilities, default behavior, or any limitations. It provides minimal but non-trivial behavioral context, so a 3.
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, front-loaded with the core purpose, and no redundancy. Efficient and well-structured, a 5.
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 but omits usage context and differentiation from the many sibling news tools. Given the schema covers parameters, the description is adequate but leaves a significant gap in guidance, so a 3.
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 input schema has 100% coverage with descriptions for q, limit, category, and timeframe. The description adds no additional parameter context, so the baseline of 3 applies.
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 'Returns' as the verb and specifies the resource ('Latest source-backed news from the Asha News archive') plus the key fields returned (publish time, source, citation links). It is clear but does not explicitly contrast with sibling tools like asha_breaking or asha_search, so it's a 4.
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 statements about when to use this tool vs alternatives. The description only states what it does without indicating exclusions or preferred use cases, so a 2.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.