Skip to main content
Glama
depsdev-mcp

depsdev-mcp

by Ankur1911

project_packages

Read-onlyIdempotent

Retrieve packages published from a source project, grouped by package with version counts and verified source-repo links listed first.

Instructions

Packages published from a source project, grouped by package with version counts. Verified source-repo links are listed first.

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": {
      "project_id": "<project_id>"
    },
    "name": "project_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum packages to return.
project_idYesSource project id such as 'github.com/expressjs/express' (GitHub, GitLab or Bitbucket).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, and idempotent behavior. The description adds useful return-shape context: results are grouped by package with version counts, and verified source-repo links are listed first. It does not cover auth, rate limits, or pagination behavior, but it adds meaningful behavior beyond the annotations.

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 tight sentences, front-loaded with what is returned and how results are ordered. Every sentence adds useful information with no redundant restatement of the tool name.

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?

For a simple two-parameter read tool with annotations and no output schema, the description gives enough detail about result grouping and ordering. It could mention limit or pagination behavior, but overall it is complete enough for correct invocation.

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 project_id and limit are already documented in the input schema. The description reinforces the source-project concept but adds no extra syntax, format, or limit semantics beyond what the schema provides. Baseline 3 is appropriate.

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?

States a specific resource: packages published from a source project, including grouping by package and version counts. It is clear what the tool returns, but it does not explicitly differentiate itself from siblings such as package_overview or dependencies.

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 purpose implies when to use it: listing packages tied to a source project. However, there is no explicit when-to-use, when-not-to-use, or alternative-routing guidance, so the agent must infer usage from the description.

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