Skip to main content
Glama

NS Pros MCP Gateway

ntsb-investigations__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": "ntsb-investigations__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 present, the description carries the burden and does real work: it names the two upstream providers, what each contributes, and enumerates the returned summary fields plus per-advisory detail and a link. It stops short of disclosing failure behavior if one upstream source is down, caching, rate limits, or whether the call is costly/slow.

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-loaded with the core purpose, then sources, then triggers, then return shape — a sensible ordering with no filler. The opening sentence is long and stacks parentheticals, but every clause contributes information an agent would otherwise lack.

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, and the description compensates by listing the summary fields and additional returns, so an agent knows what it will get back. For a zero-annotation, two-parameter composite tool the coverage is nearly sufficient; only error/partial-failure behavior and upstream cost remain unaddressed.

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%, and both parameters already document scoped package-name acceptance and the latest-version default. The description adds no parameter-level meaning beyond the schema (it mentions 'version history' only as a data source), so the 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 verb and resource: a composite 'should I add this npm package' check that fans out across deps.dev (license, advisories, version history) and bundlephobia (bundle size, dependency count, ESM support). The reader immediately knows exactly what question this tool answers and what data backs 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 ('Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me"') which maps intent directly onto the tool. It also implies batching value with 'in ONE call'. It does not state when-not to use it or name any alternative, but the sibling list contains no close competitor for this purpose.

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.