Skip to main content
Glama

Package maintenance status

Check a list of dependencies

check_packages
Read-onlyIdempotent

Check up to 10 packages from one ecosystem in one call, e.g. a project's dependency list, and get the same status, verdict and evidence for each. Flags deprecated, archived and stale dependencies.

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": {
      "ecosystem": "<ecosystem>",
      "names": "<names>"
    },
    "name": "check_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
namesYesPackage names as published.
ecosystemYesPackage ecosystem: pypi, npm, cargo, go, maven, nuget or rubygems (aliases like python, node, rust, java accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety is covered. The description adds real value beyond that: it guarantees the same status, verdict and evidence per package across the batch, and discloses what it detects (deprecated, archived, stale). It does not cover partial failures or invalid package names.

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 front-loaded sentences with no waste: the batch scope comes first, then the output and detection behavior. The example is short and earns its place by clarifying intent.

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 partially compensates by describing the per-package return (status, verdict, evidence). Annotations cover the safety profile, and the batch limit is stated. Minor gaps remain around mixed-ecosystem rejection and error handling for unknown package names.

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 both parameters are documented, including ecosystem aliases, so the baseline is 3. The description only echoes the 'one ecosystem' and 'up to 10' constraints already encoded in the schema, adding no new parameter meaning.

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 verb and resource ('Check up to 10 packages from one ecosystem in one call') and defines the batch scope, so an agent can tell it apart from a single-package sibling by the 'up to 10 in one call' framing. It stops short of naming check_package_maintenance explicitly, so differentiation is implied rather than stated.

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 phrase 'e.g. a project's dependency list' gives a concrete usage context that implies the right scenario for batching. However, there is no explicit when-not guidance and no named alternative for single-package checks, leaving the routing decision to inference.

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.

Resources