Skip to main content
Glama
Systems Manager

Systems Manager

Clean Package Cache

sm_system_clean_package_cache
Destructive

Cleans cached package files to free disk space and reduce stale package data on managed systems.

Instructions

Clean package cache (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_clean_package_cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.

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 destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it never says what is actually deleted (cached package files/downloads), whether it is reversible, or what effect it has on subsequent installs, so it leaves the destructive nature entirely to the structured fields.

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?

It is short and front-loads the action, but the second sentence ('System operations for managing packages, system health, and updates') is category boilerplate that conveys nothing about this tool and could be removed without loss.

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?

For a destructive, non-idempotent mutation with no output schema, an agent needs to know the blast radius and confirmation expectations. The definition supplies neither, and the only useful parameter guidance lives in the schema rather than the description.

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?

There is a single optional parameter and the schema documents it fully, including the default and the intended use case ('Pass true when the client cannot answer an approval prompt'). The description adds no meaning beyond that, which is the expected baseline when schema description coverage is 100%.

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?

The first clause gives a specific verb and resource: 'Clean package cache'. That is enough to tell it apart from siblings like sm_system_clean_temp_files by object, though the definition never explicitly contrasts them, and the trailing parenthetical 'sm_system_operations' is just a group label.

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?

Usage is only implied by the word 'Clean' on a package cache; there is no statement of when to prefer this over sm_system_clean or sm_system_clean_temp_files, no prerequisites, and no mention of when the confirmation parameter should be supplied.

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