Skip to main content
Glama

check_package

Read-onlyIdempotent

Free, read-only. Rescue check for one npm or PyPI package (typically an MCP server): is it still looked after? Returns a verdict — sheltered (already lives here), moved (its deprecation notice names a published successor, returned as successor: use that instead), abandoned (deprecated, archived on GitHub, PyPI-archived or Inactive), gone (unpublished), stale (no release in over a year), maintained, unknown or not-found — with the public signals behind it, the install line, and the resident's résumé, the successor's check, or a pre-filled surrender link to park an abandoned or stale package here for free. Reads registry metadata only; nothing is installed or run, and the verdict says nothing about code quality.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
registryNonpm

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety bar is lower, yet the description still adds real value: it reads registry metadata only, installs and runs nothing, and explicitly disclaims any judgment about code quality. It also discloses what comes back in each case (signals, install line, resident résumé, successor check, surrender link).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the essential framing (free, read-only, one package) and the verdict enumeration earns its space, but the single em-dash-chained sentence is dense and relies on in-group jargon such as 'already lives here', 'the resident's résumé', and 'surrender link'. Readability is traded away for compactness.

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 does the heavy lifting by enumerating every verdict and the accompanying payload, and it covers side effects and cost. Remaining gaps are minor for a two-parameter read of public registry metadata.

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 0%, so the description must carry parameter meaning; it only implicitly conveys that `registry` selects npm versus PyPI and that `name` is the single package identifier. It adds no format or edge-case guidance (scoped package names, case sensitivity, name length limit) to compensate for the undocumented schema.

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-plus-resource: a free read-only rescue check of one npm or PyPI package, typically an MCP server, returning a named verdict. The enumerated verdict vocabulary (sheltered, moved, abandoned, gone, stale, maintained, unknown, not-found) makes the tool's output scope unmistakable and separates it from lookalike registry tools.

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 clear context for invocation (a rescue check on a single package, typically an MCP server) and in-band routing advice: when a package is 'moved', use the returned `successor` instead. It stops short of naming a sibling alternative or an explicit when-not-to-use condition, so it is strong but not complete.

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.