Skip to main content
Glama

Deps Dev Version

deps_dev_version
Read-onlyIdempotent

Security advisories, license and dependency metadata for ONE specific published release of a package. Requires an exact version that this package actually shipped, if you do not already have one, call package first to list them; a version guessed or carried over from a different package will not resolve.

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": "express",
      "system_": "NPM",
      "version": "4.18.2"
    },
    "name": "deps_dev_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name as the registry spells it, scoped npm names keep the "@scope/" prefix, Go modules are the full import path, Maven is "groupId:artifactId".
system_YesNPM | PYPI | GO | MAVEN | NUGET | CARGO | RUBYGEMS
versionYesAn exact version string THIS package published. Get it from the `package` tool rather than assuming; version numbers are not transferable between packages.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Package name as the registry spells it — scoped npm names keep the \"@scope/\" prefix, Go modules are the full import path, Maven is \"groupId:artifactId\"."New value: +"Package name as the registry spells it, scoped npm names keep the \"@scope/\" prefix, Go modules are the full import path, Maven is \"groupId:artifactId\"."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds real behavioral value by disclosing that lookups fail rather than degrade when the version is guessed or carried over from another package. It does not discuss any rate limits or partial-result behavior.

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?

Two sentences, front-loaded with what the tool returns and immediately followed by the version prerequisite. Slightly run-on around the semicolon, but no filler or repetition beyond the version warning, which is worth the space.

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

Completeness5/5

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

For a simple three-parameter lookup with full schema coverage and an output schema that defines the return shape, nothing an agent needs to invoke it correctly is missing. Purpose, prerequisite workflow, and failure condition are all present.

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 the schema already spells out name formatting per registry, the system enum values, and even the warning that 'version numbers are not transferable between packages'. The description reinforces the same version constraint rather than adding new meaning, so baseline 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?

The description names the concrete resource set (security advisories, license, dependency metadata) and pins the scope to 'ONE specific published release of a package', with the emphasis on ONE separating it from the version-listing sibling. An agent knows exactly what comes back and at what granularity before opening the schema.

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

Usage Guidelines5/5

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

It states the precondition (you need an exact published version) and routes the agent explicitly: 'if you do not already have one, call `package` first to list them'. It also names the failure mode that rules out the common misuse — a guessed or cross-package version 'will not resolve'.

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.