Skip to main content
Glama

NS Pros MCP Gateway

nj-mvc__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": "nj-mvc__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

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the external data sources, and enumerates the returned summary fields (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable) plus per-advisory detail. It omits failure behavior (nonexistent package, unpublished version, upstream timeout), which matters for a tool that depends on two third-party services.

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?

It is front-loaded and dense with useful signal, but the sentence is overstuffed with parentheticals and, critically, terminates mid-list at 'link' — the return-value enumeration is visibly truncated. The trigger-phrase clause could be tighter, and the cut-off tail costs clarity on what the tool returns.

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?

There is no output schema, so the description must describe return values — and it does, naming the summary block fields and the per-advisory/link payloads. Given the tool's two-source fan-out, the main remaining gap is error/empty-result behavior, which leaves it short of fully self-sufficient but still well above 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 description coverage is 100%, so both `package` and `version` are already documented in the schema. The description mentions version history and is_latest, which lightly reinforces the `version`/latest-default semantics, but adds no format or edge-case detail beyond the schema. Baseline 3 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?

The description names a specific composite action (one-call 'should I add this npm package' check) and states the upstream sources it fans out to (deps.dev for license/advisories/version history, bundlephobia for bundle size, dep count, ESM/tree-shake). No sibling tool in the catalog does npm package vetting, so the agent can distinguish it immediately from the research/prediction tools listed.

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?

It gives explicit trigger phrases ('is X safe / popular / small', 'what does adding lodash cost me'), which maps cleanly to the agent's decision point. It stops short of saying when NOT to use it or what to do when a package is unknown/private, so usage coverage is clear but not exhaustive.

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.