Remove expired entries from the on-disk cache to free storage and keep data fresh.
Sweep expired entries from the on-disk cache.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "cache_purge"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v4.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description only says 'sweep expired entries' without disclosing the destructive nature, irreversibility, or potential side effects on the cache. With no annotations available, the description carries the full burden and fails to convey that this is a mutation operation.
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?
A single sentence that immediately states the action and target. It is front-loaded and contains no redundant or vague wording, earning a perfect conciseness score.
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 (0 parameters), the description states the core purpose. However, it lacks critical context about operational impact (e.g., that it permanently removes data, whether it blocks, or if it's part of routine maintenance), leaving the description incomplete for safe invocation.
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 coverage is trivially 100%. The description correctly does not need to explain parameters, and the baseline of 4 applies due to the absence of parameters.
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 ('sweep') and resource ('on-disk cache') to clearly state the tool's function. It unambiguously distinguishes this from sibling data-retrieval tools like get_gold_price and gold_market_snapshot.
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 guidance is provided on when to use this tool or when to avoid it. The description does not mention alternatives, prerequisites, or typical scenarios, leaving the agent to infer usage solely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.