NPM Sentinel MCP

npmSearch

Read-only

Search NPM packages by query, set result limit, and bypass cache for fresh results.

Instructions

Search for NPM packages with optional limit

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of results to return (default: 10)
`query`	Yes	Search query for packages
`ignoreCache`	No	Force a fresh lookup, ignoring the cache

Output Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No
`message`	No
`results`	No
`limitUsed`	No
`resultsCount`	No
`totalResults`	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

A4/5.0

Behavior4/5

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

Annotations already provide readOnlyHint and openWorldHint. The description adds context about the optional limit and implicitly caching via ignoreCache parameter, but does not elaborate on caching effects or data freshness beyond schema.

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?

Extremely concise single sentence, front-loaded with key information. No wasted words.

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?

For a simple search tool with output schema, the description is almost complete. It might benefit from a brief note on search behavior (e.g., exact vs fuzzy), but not essential.

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?

With 100% schema coverage, each parameter has a description. The description only redundantly mentions 'optional limit' without adding new meaning beyond the schema.

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 description clearly states the verb 'Search' and resource 'NPM packages' with the optional limit parameter. It distinguishes itself from sibling tools like npmVersions or npmLatest which target specific aspects.

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 explicitly advise when to use this tool versus siblings. It states the core function but lacks guidance on alternatives or when not to use it.

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