Clears cached AMFI mutual fund NAV data so the next request retrieves fresh values; use it after AMFI publishes daily NAVs to avoid viewing stale 24-hour cache.
Clear cached AMFI data so the next call fetches fresh NAVs.
NAVs are cached for 24 hours. AMFI usually publishes the day's NAVs after about 9 PM IST, so clear the cache after that to see them.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears the full burden of transparency. It explains the functional impact ('so the next call fetches fresh NAVs') and the constraint (24-hour cache limit), adding high-value behavioral context.
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 highly efficient. Both sentences provide crucial, distinct pieces of information (what it clears and when to use it) with zero wasted words.
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 that this is a zero-parameter tool, the definition is maximally complete. It informs the agent when, why, and how this tool functions in the broader data retrieval workflow.
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?
Since there are no parameters, the baseline score of 4 applies. The description adds value by defining the nature of the data being acted upon (AMFI data) rather than just leaving the action undefined.
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 tool's purpose: to 'Clear cached AMFI data.' This is a specific action that clearly distinguishes it from the sibling data retrieval and calculation 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?
It provides critical usage context by defining the cache lifespan (24 hours) and giving specific timing advice ('clear the cache after [9 PM IST]') based on external data publication schedules.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.