Skip to main content
Glama
SLF Guardian MCP

SLF Guardian MCP

by slfguardian

check_package

Check a PyPI or npm package before you install or recommend it. Returns a verdict and safe_to_install flag covering existence, age, downloads, install scripts, deprecation, and known vulnerabilities.

Instructions

Check a PyPI or npm package before installing or recommending it. Asks the registry whether the name exists at all (invented package names are how slopsquatting attacks land), how old it is, how much it is downloaded, whether it runs install scripts, whether it is deprecated or yanked, whether OSV lists vulnerabilities, and whether the name is a near-miss of a popular package. Returns a verdict and a safe_to_install flag.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "check_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoPackage name.
versionNoOptional exact version to check.
packagesNoCheck several packages in one call.
ecosystemNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses the registry lookups performed, the risk classes covered, and the shape of the response ('a verdict and a safe_to_install flag'). It does not state read-only/no-side-effect guarantees explicitly or mention rate limits or failure behavior for nonexistent packages, which keeps it short of a 5.

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?

The purpose and the pre-install trigger are front-loaded, and the enumeration of checks is dense but each clause conveys a distinct signal. The single long sentence is slightly list-heavy but contains no filler.

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 read-check tool with no annotations and no output schema, the description supplies the essential behavioral picture and even summarizes the return values. It could go further on batch-call semantics and the possible verdict values, but nothing critical for correct invocation is missing.

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 75%, so the schema already documents most fields. The description adds no meaning about the optional `version` pin, the `packages` batch array, or whether `name` and `packages` can be combined, leaving the batching semantics to the schema alone. Baseline 3 is appropriate here.

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?

The description names a specific verb and resource ('Check a PyPI or npm package') and enumerates exactly what is inspected: existence, age, download volume, install scripts, deprecation/yank status, OSV vulnerabilities, and name near-misses. That is clearly distinct from siblings like check_domain or check_command, so an agent can select it without opening the schema.

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?

It gives a concrete decision point ('before installing or recommending it') and explains the risk it guards against (slopsquatting via invented names). It stops short of naming alternatives or stating when not to use it, but the usage context is unambiguous.

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