Skip to main content
Glama
Systems Manager

Systems Manager

List Upgradable Packages

sm_system_list_upgradable_packages
Read-onlyIdempotent

Lists packages with available updates so you can identify what needs upgrading before patching a system.

Instructions

List upgradable 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_upgradable_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 fully covered by structured data. The description adds nothing beyond that: it does not say which package manager(s) are consulted, whether the result depends on cached/stale metadata, or whether elevated privileges affect the output. The second sentence is a category restatement, not behavioral context.

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 first clause is tight and front-loaded, but the parenthetical module tag and the trailing 'System operations for managing packages, system health, and updates' are boilerplate that consumes space without informing selection or invocation.

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-argument read-only list tool the definition is functionally sufficient to invoke, but with no output schema present the description could have stated what a result entry contains (package name, current version, available version) and whether the list can be empty. That omission leaves the agent guessing about the return shape.

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 nothing for the description to disambiguate; the baseline of 4 applies. The description introduces no misleading hints about inputs.

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?

States a specific verb and resource ('List upgradable packages'), which is immediately understandable and distinguishes it from mutation siblings like sm_system_install_local_package. It does not, however, differentiate itself from adjacent read tools such as sm_system_list_installed_packages or sm_system_get_package_info beyond the noun 'upgradable'.

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 guidance on when to call this versus sm_system_list_installed_packages or sm_system_get_package_info, nor any stated precondition (e.g., requires a refresh/sync of package metadata first). The agent must infer usage entirely from the name.

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