Skip to main content
Glama

Deps Dev Package

deps_dev_package
Read-onlyIdempotent

Fetch deps.dev metadata for an open-source package by ecosystem (NPM/PYPI/GO/MAVEN/NUGET/CARGO/RUBYGEMS) and name, returning version list, latest version, and linked source repository.

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": "lodash",
      "system_": "NPM"
    },
    "name": "deps_dev_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
system_YesNPM | PYPI | GO | MAVEN | NUGET | CARGO | RUBYGEMS

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive, so the safety profile needs no restating. The description adds the shape of the result (versions, latest, repo link), but says nothing about behavior for missing packages, rate limits, or whether the ecosystem token is case-sensitive.

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?

A single sentence that front-loads the action and resource, then states the ecosystem universe and the return contents. No filler, no repetition, nothing an agent must scan past.

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?

A two-parameter, read-only lookup with a full annotation set and an output schema; the description covers purpose, scope, and return contents, so an agent can invoke it confidently. The only meaningful omission is failure behavior for an unknown package or ecosystem.

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?

With 50% schema coverage, the 'name' parameter is undocumented in the schema and the description only restates that lookup is 'by ... name'. The ecosystem list in the description duplicates the values already given in the system_ property description, and it calls it 'ecosystem' while the field is named 'system_', which adds a small mapping burden rather than clarity.

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?

Names a specific verb and resource ('Fetch deps.dev metadata for an open-source package') and scopes it by ecosystem and name, plus what comes back (version list, latest version, source repo). It does not explicitly distinguish itself from sibling lookups like deps_dev_version or deps_dev_project, so an agent must infer that this is the package-level aggregate view.

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 pairing of ecosystem plus name suggests this is the entry-point lookup for a package. There is no statement of when to prefer it over the sibling version/project/dependencies tools, and no guidance on unknown-package behavior or ecosystem casing.

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.