Skip to main content
Glama

NS Pros MCP Gateway

numverify__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": "numverify__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.1/5.0
Behavior4/5

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

With no annotations at all, the description carries the whole disclosure burden and does well: it reveals the composite fan-out to two external services and what each contributes, which tells the agent this is a read-only lookup with no side effects and hints that results depend on upstream availability. It omits failure/partial-result behavior, rate limits, and whether results are cached, which is the remaining gap for an unannotated tool.

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?

It is front-loaded: the one-call composite value proposition and the source list come first, then usage triggers, then return shape. The sentences are dense but each carries signal; the final clause ("per-advisory detail, link") reads as truncated and slightly undercuts polish.

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 characterize returns, and it does so concretely by listing the summary fields (is_latest, license, advisory_count, bundle_kb_gz, has_esm, tree_shakeable) plus per-advisory detail and links. For a two-parameter read-only tool that is close to complete; only error/partial-failure semantics are missing.

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 parameters (package, version) are already fully documented, including scoped-package support and the latest-version default. The description adds only indirect meaning via "is_latest" and "version history" in the return summary, so the baseline 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 description names a specific verb+resource ("should I add this npm package to my project" check) and enumerates the exact data sources it fans out across (deps.dev for license/advisories/version history, bundlephobia for size/deps/ESM). An agent can tell immediately this is the npm-ecosystem safety/size evaluator rather than a generic provider scan.

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 concrete trigger questions ("is X safe / popular / small", "what does adding lodash cost me") that map directly to the intent an agent would have. It does not state when NOT to use it or point to a narrower sibling for partial needs (e.g., license-only or size-only lookups), so it stops short of full routing guidance.

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.