NPM Sentinel MCP

npmLatest

Read-onlyIdempotent

Retrieve current versions and changelogs for multiple NPM packages in a single request.

Instructions

Get the latest version and changelog of an NPM package

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": {
      "packages": "<packages>"
    },
    "name": "npmLatest"
  }
}

Input Schema

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

Output 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

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so description's burden is lower. It adds the return type (version and changelog) but doesn't elaborate on caching behavior or other traits beyond the schema's ignoreCache parameter.

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

Conciseness4/5

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

Single sentence, no fluff, front-loaded with key information. Could be slightly more structured but remains highly concise and readable.

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

Completeness3/5

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

Output schema exists so return values need not be detailed. However, with many sibling tools, a brief note on batch capability (up to 25 packages) would improve completeness. Still, given low complexity, it's minimally adequate.

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 both parameters documented in the schema. Description does not add any extra meaning or usage hints for the parameters beyond what the JSON schema provides.

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?

Description clearly states it gets the latest version and changelog of an NPM package, using specific verb and resource. This distinguishes it from siblings like npmVersions (which likely returns all versions) and npmChangelogAnalysis (analysis-focused).

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 explicit guidance on when to use this tool versus alternatives like npmVersions or npmChangelogAnalysis. It doesn't mention limitations, prerequisites, or when to avoid using it.

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