AgentsID Guard

Official

Overview Schema Source Related Servers Discussions Admin

package_list

List installed packages across npm, pip, brew, or apt managers. Provides a clear package inventory to verify compliance and audit systems.

Instructions

List installed packages. Requires package.read.

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": "package_list"
  }
}

Input Schema

Name	Required	Description	Default
`manager`	No	Package manager

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses the required permission 'package.read', which is useful, but does not explicitly state read-only behavior, output format, or potential side effects. This adds some transparency but leaves gaps.

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?

The description is two concise sentences, front-loaded with the core purpose and followed by the permission requirement. Every word earns its place; no redundancy.

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

Completeness2/5

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

The description is incomplete for this simple tool: it does not explain the behavior of the 'manager' parameter (e.g., what 'auto' does or how it affects results) nor the return format. Since there is no output schema, the description should have elaborated on what 'list installed packages' returns (names, versions, structure).

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% with 'manager' described as 'Package manager' and an enum. The description adds no additional meaning about the parameter, so the baseline of 3 applies.

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 'List installed packages' uses a specific verb and resource, and clearly distinguishes this tool from siblings like package_info and package_install. It states exactly what the tool does without ambiguity.

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 description implies usage (when you want to list installed packages) but does not provide explicit guidance on when to use this tool versus alternatives like package_info or package_install. No exclusions or alternative recommendations are mentioned.

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