Skip to main content
Glama
depsdev-mcp

depsdev-mcp

by Ankur1911

version_details

Read-onlyIdempotent

Retrieve key facts for a package version, including licences, publish date, deprecation status, source projects, provenance, and resolved security advisories with severity.

Instructions

Facts about one package version: licences, publish date, deprecation, source projects, provenance flag, and its known security advisories with severity (already resolved, no extra calls needed).

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

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 profile is covered. The description adds one genuinely useful behavioral detail — security advisory data is bundled into the response rather than requiring additional calls. It says nothing about error behavior for unknown package/version combinations or how missing fields (e.g., no provenance) are represented.

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?

A single sentence with no filler, front-loading the resource before the field list. The field enumeration is dense but each item corresponds to real return content, so nothing is wasted.

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 carries the burden of describing return values and does so by enumerating the returned facts, which is appropriate for a read-only lookup. Annotations cover safety and the schema covers all parameters, so remaining gaps (error cases, absent-field handling) are minor for this complexity level.

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 every parameter is already documented, including the version default of latest stable and the system-specific naming conventions. The description adds no syntax, format, or edge-case guidance beyond that, which is the expected baseline when the schema does the heavy lifting.

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 specific resource (one package version) and enumerates the returned facts: licences, publish date, deprecation, source projects, provenance, and advisories with severity. The parenthetical 'already resolved, no extra calls needed' implicitly separates it from the advisory sibling, but it never names that sibling or another alternative explicitly.

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 only implied: the note that advisories come pre-resolved tells an agent it need not make a separate advisory call. There is no explicit statement of when to pick this over package_overview or project_packages, and no conditions or exclusions are given.

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