Skip to main content
Glama

Package maintenance status

Check if a package is still maintained

check_package_maintenance
Read-onlyIdempotent

Is an open-source package still maintained, or is it deprecated, archived or abandoned? Use before adding, upgrading or auditing a dependency. Returns a status (active, slowing, stale, deprecated, archived, inactive, unknown, not_found), a one-sentence verdict, and the evidence: last release date and version, releases in the last 12 months, the registry deprecation flag and message (often names the replacement), the source repository, whether it is archived on GitHub and its last push, and the OpenSSF Scorecard "Maintained" score. Ecosystems: pypi, npm, cargo, go, maven (group:artifact), nuget, rubygems. Live data from deps.dev, PyPI and GitHub, cached 24 h.

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>",
      "name": "<name>"
    },
    "name": "check_package_maintenance"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name as published, e.g. requests, @types/node, serde, github.com/pkg/errors, com.google.guava:guava, Newtonsoft.Json.
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

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/openWorld, and the description adds substantial context beyond that: the exact status vocabulary, the evidence returned (last release, 12-month release count, registry deprecation flag and message, GitHub archive state, OpenSSF Maintained score), the data sources, and 24-hour caching. The caching note in particular tells the agent results may lag reality, which is behavior no annotation conveys.

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?

It is front-loaded with the core question, then usage, then a compact enumeration of output and sources. The ecosystem list appears in both the description and the schema, a minor redundancy, but every other clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing return values, and it does so fully by naming all eight status values and each supporting evidence field. For a two-parameter read-only lookup, an agent has everything required to call it and interpret the result.

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 coverage is 100%, so both parameters are already fully documented in the input schema with examples. The description restates the ecosystem list and the maven group:artifact form, which duplicates rather than extends the schema. Baseline 3 is appropriate 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 opening question names a specific resource and action: determining whether an open-source package is maintained, deprecated, archived, or abandoned. The scope is unambiguous and an agent can map a dependency-audit need to it immediately. It does not name or distinguish itself from the sibling check_packages, which is the only thing keeping it from a 5.

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?

"Use before adding, upgrading or auditing a dependency" gives concrete trigger contexts, which is stronger than the typical implied-usage case. It stops short of explicit exclusions or naming check_packages as the batch alternative, so the when-not side is left 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