Skip to main content
Glama
depsdev-mcp

depsdev-mcp

by Ankur1911

requirements

Read-onlyIdempotent

Retrieve a package version's declared dependency constraints in each ecosystem's native format, including npm dependencies and devDependencies with version ranges.

Instructions

Declared dependency constraints of a version, in the ecosystem's own form (for example npm dependencies and devDependencies with version ranges). Works for all systems, including go, nuget and rubygems.

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

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety and idempotency profile is covered structurally. The description contributes the return shape — ecosystem-native ranges such as npm dependencies and devDependencies — which is valuable given there is no output schema. It says nothing about empty results, unresolvable versions, or whether constraints are raw declarations versus resolved ranges beyond the word 'declared'.

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, no filler, with the core definition front-loaded and the portability caveat second. Every phrase carries information and nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with no output schema, describing the returned form is the right instinct and the description does that. The remaining gap is disambiguation: a sibling literally named 'dependencies' exists and the description never distinguishes declared constraints from resolved dependencies, leaving the agent to guess.

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 both the 'name' format and the 'system' enum conventions (Maven group:artifact, Go module paths) are already fully documented in the schema. The description adds nothing about individual parameters, so the baseline of 3 applies.

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 states a specific resource: the declared dependency constraints of a version, rendered in the ecosystem's native form. That is concrete enough for an agent to know it returns manifest-style requirement data rather than resolved dependencies. It stops short of differentiating itself from the sibling tool named 'dependencies', which is the most likely source of confusion.

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?

The clause 'Works for all systems, including go, nuget and rubygems' gives useful coverage context and implicitly widens the conditions under which the tool applies. However, there is no explicit when-to-use statement and no exclusion telling the agent when to prefer the sibling 'dependencies' or 'version_details' instead.

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