Skip to main content
Glama

Deps Dev Dependencies

deps_dev_dependencies
Read-onlyIdempotent

The fully resolved dependency graph of one published release, every transitive package it pulls in. Same requirement as version: the version must be one this package actually shipped, so call package first if you are not certain.

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": {
      "name": "webpack",
      "system_": "NPM",
      "version": "5.88.0"
    },
    "name": "deps_dev_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name as the registry spells it.
system_YesNPM | PYPI | GO | MAVEN | NUGET | CARGO | RUBYGEMS
versionYesAn exact version string THIS package published, from the `package` tool, not assumed.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / version / description
      Previous value: -"An exact version string THIS package published — from the `package` tool, not assumed."New value: +"An exact version string THIS package published, from the `package` tool, not assumed."
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds a genuine behavioral constraint — the version must be one the package actually shipped, otherwise the call fails — but it says nothing about the size/shape of the returned graph or whether direct dependencies are included alongside transitive ones.

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 definition and followed by the one precondition an agent must satisfy. There is no filler or restatement of the 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 an output schema present and rich annotations, the description does not need to explain return values or safety. It covers the essential lookup precondition; only minor ambiguities remain, such as whether the graph includes direct dependencies alongside transitive ones and whether large graphs are paginated or truncated.

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 all three parameters, including the enumeration of supported systems, are already documented in the schema. The description's note about the `version` requirement largely restates what the schema's `version` description already says ('an exact version string THIS package published, from the `package` tool, not assumed'), adding little new meaning.

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 the resource precisely — 'the fully resolved dependency graph of one published release, every transitive package it pulls in' — which is far more specific than the bare title. It also implicitly distinguishes itself from `version` and `package` by referencing them, though it never states outright how it differs from `version` (which presumably also takes a version but returns different data).

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?

It gives a concrete prerequisite: 'call `package` first if you are not certain', which tells the agent how to obtain a valid `version` value. What is missing is an explicit statement of when to reach for this tool versus `version` or `project` (e.g., when you need the transitive closure rather than direct or declared dependencies).

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.