Clear cached npm package data to refresh version, health, or popularity results; optionally filter by package name or cache type.
Clear cached npm package data. Optionally filter by package name or cache type (versions, health, popular)
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Cache type to clear: versions, health, popular, or all (default) | |
| package | No | Package name to clear cache for, or omit to clear all |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It never states whether a clear is destructive/irreversible, whether omitting both filters wipes the entire cache, whether it requires elevated permissions, or what happens to in-flight consumers of the cache.
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 short sentences with the core action front-loaded and the filtering behavior immediately after. No filler or repetition.
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?
For a simple two-parameter tool with a fully described schema and no output schema, the description covers what an agent needs to invoke it. The only shortfall is the undocumented default (clearing everything when no filters are given), which is left implicit.
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%, so both parameters and the enum are already fully documented in the schema; baseline 3 applies. The description restates the enum values but omits the "all" default, adding no meaning beyond the schema.
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?
States a specific verb and resource: clear cached npm package data. The sibling tools (boop, sniff, big-sniff-file, big-sniff-list) share the pkg-booper prefix but have no overlapping purpose, so there is nothing to disambiguate against.
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?
"Optionally filter by package name or cache type" implies the tool can be used globally or scoped, but there is no explicit when-to-use guidance, no prerequisites, and no statement about when clearing the whole cache is preferred over a scoped clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.