Skip to main content
Glama

NS Pros MCP Gateway

npi-registry__scan_dependency

Composite "should I add this npm package to my project" check in ONE call, fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, link

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "package": "left-pad"
    },
    "name": "npi-registry__scan_dependency"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYesnpm package name. Scoped packages (e.g. "@types/node") are accepted.
versionNoSpecific version to check (e.g., "18.3.1"). Defaults to the latest published version when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the important structural behavior — a single call fans out to two external services and returns a summary block plus per-advisory detail — which is genuinely useful. However, it says nothing about latency or upstream-failure behavior (what happens if deps.dev or bundlephobia is down or the package is missing), nor about caching or rate limits, and the final clause is cut off mid-sentence.

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?

Front-loads the one-call composite value proposition before listing sources and return fields, so an agent can decide quickly. The sentences are dense and slightly run-on, and the trailing "link" fragment indicates the description is truncated, which is a structural flaw but not wasted wording.

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?

No output schema exists, so the description helpfully enumerates the summary keys (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable) plus per-advisory detail. That is close to complete for a two-parameter read-style tool; only failure/partial-result behavior and the truncated ending keep it from a 5.

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%, with both `package` and `version` documented including scoped-package syntax and the default-to-latest behavior. The description adds no parameter information beyond that, so the baseline 3 for high-coverage schemas applies.

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?

States a specific composite verb+resource: a "should I add this npm package to my project" check in one call, and names the two upstream sources (deps.dev for license/advisories/version history, bundlephobia for size/dependency count/ESM). The intent and scope are unambiguous, and no sibling tool in the list overlaps with it.

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

Usage Guidelines4/5

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

Gives explicit trigger phrasing — "is X safe / popular / small" or "what does adding lodash cost me" — which tells an agent exactly which question shapes should route here. It stops short of stating when NOT to use it (e.g. when only a version lookup is needed, or when the package isn't on npm), so it earns a 4 rather than a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.