Skip to main content
Glama
Systems Manager

Systems Manager

List Installed Packages

sm_system_list_installed_packages
Read-onlyIdempotent

Lists installed packages on a managed system to help you audit software, verify package state, and plan updates.

Instructions

List installed packages (sm_system_operations). System operations for managing packages, system health, and updates

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond the annotation set — no statement about scope (all packages vs. user-installed), output shape, pagination, or whether elevated privileges are needed for a system-wide package listing.

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?

The core purpose is front-loaded in the first clause and the total length is minimal. But the trailing category sentence and the parenthetical namespace reference carry no decision-relevant information and do not earn their place.

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

Completeness3/5

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

For a zero-parameter read-only listing tool with no output schema, the description states what is returned at a high level (installed packages) and annotations cover safety. It is still thin on scope and result characteristics, which would matter to an agent deciding between this and the upgradable-packages or get-package-info siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics for the description to explain. Baseline 4 applies; the description correctly avoids inventing filtering options that the schema does not support.

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?

"List installed packages" is a specific verb+resource pair that an agent can act on immediately, and it is distinguishable in principle from siblings like sm_system_list_upgradable_packages or sm_system_get_package_info. However, the description never explicitly contrasts itself with those siblings, leaving the differentiation to name inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no when-not-to-use condition, and no named alternative for checking upgradable packages or package details. The second sentence ("System operations for managing packages, system health, and updates") is a generic category label rather than routing guidance.

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

Deploy Server

Other Tools