Skip to main content
Glama
depsdev-mcp

depsdev-mcp

by Ankur1911

audit_package

Read-onlyIdempotent

Run a one-call security and hygiene review for a package version: check licences, deprecation, advisories by severity, and vulnerable dependencies.

Instructions

One-call security and hygiene review of a package version: licences, deprecation, its own advisories by severity, and which of its dependencies (direct first) have known advisories. Replaces many separate lookups.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "system": "<system>",
      "name": "<name>"
    },
    "name": "audit_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact package name as published in its registry.
systemYesPackage ecosystem. Maven names are 'group:artifact'; Go names are module paths such as github.com/gin-gonic/gin.
versionNoVersion string. Omit to use the package's default (latest stable) version.
max_dependenciesNoCap on dependencies checked for advisories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, and open-world behavior, so the safety profile is covered. The description adds useful scope detail (which categories are checked, and that dependencies are reviewed 'direct first'), but says nothing about how the max_dependencies cap affects the result, whether truncation is surfaced, or what happens for unknown packages/versions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence followed by a short positioning clause; the audit subject is front-loaded and every phrase (licences, deprecation, severity breakdown, dependency advisories) carries information an agent would otherwise have to infer.

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?

With no output schema, the description usefully enumerates what the result covers, which is most of what an agent needs to decide on and interpret the call. Minor gaps remain around truncation reporting and error behavior for invalid package/version combinations.

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%, including the ecosystem enum values and the default-version omission behavior, so the schema carries the parameter burden. The description only indirectly hints at dependency traversal order ('direct first'); it adds no syntax or format guidance beyond the schema, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource ('One-call security and hygiene review of a package version') and enumerates the exact facets covered: licences, deprecation, own advisories by severity, and dependency advisories. That is enough to distinguish it from siblings like advisory or dependencies, which cover single facets, though it never names those siblings explicitly.

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?

'Replaces many separate lookups' signals the intended use case: a consolidated audit rather than piecemeal calls to the advisory/dependencies tools. It stops short of explicit exclusions (e.g., when to prefer a single targeted lookup for cost or freshness reasons), but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.