Skip to main content
Glama
Sign In
npm-mcp

npm-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

cache

Manage the npm cache: clear outdated packages to free disk space, verify cache integrity to prevent corruption, or list cached contents to inspect stored packages.

Instructions

Manage the npm cache

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoForce clean (required for clean action)
actionYesAction: clean (clear cache), verify (check integrity), ls (list contents)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description must fully disclose behavior. It does not mention that 'clean' is destructive, that 'verify' checks integrity without side effects, or that 'ls' lists contents. The description provides no behavioral traits beyond the generic term 'manage'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two words) but not structured as a proper sentence. It is concise but under-specified, lacking crucial details that a complete sentence would provide.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool supports three distinct actions and has a required force flag, the description is insufficient. It does not explain output, error conditions, or effects, and without an output schema, the agent lacks essential context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and already explains the 'action' enum and 'force' parameter. The description adds no additional semantics beyond the schema, meeting the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource (npm cache) but uses the vague verb 'manage'. It does not distinguish from sibling tools like 'ls' or 'install', but the schema's action enum provides specificity. Accordingly, it is clear but lacks sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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 versus alternatives (e.g., when to clean vs verify, or when to use other tools like 'install' for cache-related tasks). There are no hints about prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools