Skip to main content
Glama

NS Pros MCP Gateway

nsf-awards__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": "nsf-awards__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 supplied, the description carries the full burden and does well: it discloses the two upstream sources queried, the fact that it fans out in one call, and enumerates the returned summary fields (is_latest, license, advisory_count, bundle_kb_gz, has_esm, tree_shakeable), which compensates for the absent output schema. It omits failure behavior for nonexistent packages, rate limits, and latency expectations for the two-source 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?

Front-loaded with the core purpose, then sources, then triggers, then return shape - a sensible ordering with essentially no filler sentences. The final clause "per-advisory detail, link" trails off awkwardly and could be tightened, but overall it is dense and efficient.

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-parameter read-style tool with no annotations and no output schema, the description covers purpose, data sources, invocation trigger, and return fields - enough for an agent to call it correctly and interpret the response. Only error/empty-result behavior is 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 (package, version) are documented in-schema including scoped-package support and the default-to-latest behavior. The description adds no parameter-level meaning beyond the examples implied by "X" and "lodash", 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, and names exactly what it aggregates (deps.dev for license/advisories/version history, bundlephobia for bundle size, dependency count, ESM/tree-shake). Nothing among the sibling tools overlaps with npm package evaluation, so the tool is unambiguously identifiable.

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?

Provides concrete trigger conditions in natural agent phrasing: "is X safe / popular / small" or "what does adding lodash cost me", which tells the agent exactly when to reach for this. It does not state when not to use it or name any alternative, but no sibling offers comparable functionality, so the omission is minor.

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.