NPM Sentinel MCP

npmDeps

Read-onlyIdempotent

Analyze dependencies and devDependencies of NPM packages to identify their composition, aiding in vulnerability checks and quality assessment.

Instructions

Analyze dependencies and devDependencies of an NPM package

Input Schema

TableJSON Schema

Name	Required	Description	Default
`packages`	Yes	List of package names to analyze dependencies for
`ignoreCache`	No	Force a fresh lookup, ignoring the cache

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	No
`results`	No
`summary`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.24.0Jul 28, 2026
Removedv1.23.0Jul 25, 2026
Changed2 schema fields changedv1.20.0Jul 13, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / ignoreCache
```
Added value: +{
+  "description": "Force a fresh lookup, ignoring the cache",
+  "type": "boolean"
+}
```
First observedv1.0.0Aug 14, 2025

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds that it analyzes both dependencies and devDependencies, but does not disclose additional behavioral traits like caching behavior or data freshness. It does not contradict annotations.

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

Conciseness5/5

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

The description is a single sentence that is front-loaded with the action and resource. Every word is necessary, and there is no extraneous information.

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

Completeness4/5

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

Given the presence of a complete output schema, full parameter descriptions, and annotations, the tool definition is mostly complete. The description could mention that it returns a list of dependencies, but it is not essential due to the output schema.

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 coverage is 100% with descriptions for both 'packages' and 'ignoreCache'. The description does not add any meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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

Purpose5/5

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

The tool name 'npmDeps' and description 'Analyze dependencies and devDependencies of an NPM package' clearly specify the action and resource. It distinguishes itself from sibling tools like npmVersions or npmLatest, which have different purposes.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention when not to use it. The context of sibling tools implies its unique purpose, but the description itself lacks usage instructions.

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