Skip to main content
Glama

NS Pros MCP Gateway

nobel__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": "nobel__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, the description carries the full burden and does disclose meaningful behavior: that the tool fans out across two external services, which data each supplies, and the shape of the summary block plus per-advisory detail and link. It omits failure semantics - what happens for unpublished/private packages, missing versions, or when bundlephobia has no data - and says nothing about latency or rate limits despite the multi-service fan-out.

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?

The purpose and the return contract are front-loaded in the opening clause, so the key information lands immediately. The long enumeration of summary fields is justified because no output schema exists, though the multi-clause run-on construction makes it denser than necessary.

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 two-source aggregation tool with no output schema, the description supplies the return structure (summary fields, per-advisory detail, link) and the data provenance, which is what an agent needs to interpret results. The remaining gap is error/degraded-source behavior for a tool that depends on two external APIs.

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' (including scoped names) and 'version' (defaulting to latest) fully documented in the schema itself. The description adds only the illustrative 'lodash'/'X' example and does not extend version or package semantics beyond that, so the schema baseline of 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?

States a specific check (composite 'should I add this npm package' evaluation) and enumerates the two upstream sources and the exact facets each contributes. The parenthetical field list ('is_latest, license, published_at, advisory_count...') makes the resource and scope unambiguous, so an agent knows precisely what a call produces without opening the schema.

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 concrete trigger phrasing ('Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me"') and signals that this is a single-call aggregation rather than separate per-source lookups. It does not explicitly state when NOT to use it or name an alternative tool for single-facet checks, so it stops short of level 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.