Skip to main content
Glama
Systems Manager

Systems Manager

Clean

sm_system_clean
Destructive

Cleans system packages and related files to free storage and remove outdated data; set confirm=true to authorize the cleanup.

Instructions

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

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

C2.3/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 known. The description adds nothing on top: it never says what is removed, whether it is recoverable, whether admin rights are needed, or how long it takes. For a destructive tool this is a meaningful omission rather than a neutral one.

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, but the brevity is under-specification, not efficiency: the parenthetical namespace restates metadata and the second sentence is category boilerplate with no front-loaded information about the tool's actual effect. There is little to cut, but also little that earns its place.

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?

This is a destructive, non-idempotent operation with no output schema, and the description supplies no scope, target, or consequence information to compensate. The annotations plus the confirm parameter describe the risk level but not the blast radius, which is exactly what an agent needs before invoking a clean operation.

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?

With a single parameter at 100% schema description coverage, the schema's explanation of confirm (pass true when the client cannot answer an approval prompt) fully carries the semantics. The description contributes nothing about confirm, which is the baseline-3 outcome when the schema does the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Clean" alone is a bare verb with no resource, effectively restating the name and title. The only added sentence — "System operations for managing packages, system health, and updates" — describes the whole sm_system_* family rather than this tool, so it does nothing to distinguish it from siblings like sm_system_clean_package_cache or sm_system_clean_temp_files. An agent cannot tell what actually gets cleaned.

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 prerequisites, and no mention of the more specific clean siblings that would normally be preferred. The agent must guess whether this is a general-purpose sweep or an alias for one of the narrower clean tools.

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