Skip to main content
Glama
depsdev-mcp

depsdev-mcp

by Ankur1911

package_overview

Read-onlyIdempotent

Summarise a package's default version, version count, deprecation status and recent releases. Use it to choose the right version before querying licences, advisories or dependencies.

Instructions

Summarise a package: default version, number of versions, how many are deprecated, and the most recently published versions. Use this first to pick a version for the other tools.

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

Input Schema

NameRequiredDescriptionDefault
nameYesExact package name as published in its registry.
recentNoHow many recent versions to list.
systemYesPackage ecosystem. Maven names are 'group:artifact'; Go names are module paths such as github.com/gin-gonic/gin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 the workflow placement of the call and hints at the shape of the result, but says nothing about authentication needs, registry latency, or failure behavior when a package or ecosystem lookup misses.

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 short sentences with no waste: the first front-loads the returned content, the second front-loads the usage rule. Nothing is repeated from the schema or 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 no output schema present, the description carries the burden of describing return values and does it by listing the four things returned. For a three-parameter, read-only summary tool this is nearly complete, with only edge-case behavior (unknown package, empty recent list) left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameters are already well documented, including the enum and the Maven/Go naming conventions. The description lightly reinforces the 'recent' parameter by mentioning most recently published versions, adding a little meaning on top of the schema baseline of 3.

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?

States a specific verb (summarise) and resource (a package) and enumerates exactly what the summary contains: default version, version count, deprecated count, and recently published versions. Combined with the closing line positioning it as the entry point 'for the other tools', an agent can tell it apart from version_details or requirements without opening a schema.

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?

Gives explicit sequencing guidance — 'Use this first to pick a version for the other tools' — which is unusually actionable for a discovery tool. It stops short of naming a specific alternative or stating when not to use it, so it is clear context rather than a full routing rule.

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