Skip to main content
Glama
depsdev-mcp

depsdev-mcp

by Ankur1911

dependencies

Read-onlyIdempotent

List resolved direct or transitive dependency data for a package version across npm, PyPI, Cargo, Go, Maven, NuGet, or RubyGems, with counts and scope filtering.

Instructions

List the resolved dependencies of a version (npm, cargo, maven, pypi). Returns direct and indirect counts; scope 'direct' lists only direct dependencies, 'all' includes the transitive ones.

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": "dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact package name as published in its registry.
limitNoMaximum dependencies to return.
scopeNoWhich dependencies to list.direct
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds value beyond that by disclosing the return shape (direct and indirect counts) and the exact behavioral meaning of each scope value. It omits truncation/pagination behavior against the 'limit' cap, which is the only notable gap.

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?

Two sentences, front-loaded with the core action, and the second sentence carries only the return-shape and scope semantics. Nothing is redundant with the name or title.

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 five parameters, 100% schema coverage and no output schema, the description is nearly sufficient: it conveys what the call returns and how scope changes results. The ecosystem list ('npm, cargo, maven, pypi') is narrower than the schema enum (which also includes go, nuget and rubygems), leaving a minor mismatch an agent might notice.

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 the baseline is 3; the schema already defines name, limit, version and both enums. The description does add one piece of meaning beyond the schema by explaining that 'direct' versus 'all' controls transitive inclusion, but it adds nothing for version resolution or limit.

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 first clause names a specific verb and resource ('List the resolved dependencies of a version') and enumerates ecosystems, so the agent knows exactly what is produced. It stops short of differentiating itself from siblings such as 'requirements' or 'version_details', which read as adjacent capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the phrase 'dependencies of a version', which signals a per-version dependency query. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. 'requirements' or 'version_details') to route the agent between them.

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