Skip to main content
Glama
Systems Manager

Systems Manager

Clean Temp Files

sm_system_clean_temp_files
Destructive

Removes temporary system files to free disk space and reduce clutter; supports confirmation for mutating cleanup actions.

Instructions

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

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.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: it does not say which directories or file classes get deleted, what happens on partial failure, or whether cleanup is reversible, which matters for a destructive operation.

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 text is short and front-loads the operation, but the trailing category sentence is boilerplate that does not earn its place. Half the description is non-informative filler.

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 system operation with no output schema, the description should convey scope (what temp files, which locations) and consequences. Instead it stops at the tool name plus a generic category sentence, leaving the agent unable to judge blast radius.

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 parameter (confirm) with 100% schema description coverage, so the schema already explains its purpose and default. The description adds no meaning about when confirmation is required or what happens if it is omitted, which yields the baseline 3.

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

Purpose3/5

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

The first clause names a specific verb and resource ('Clean temp files'), which is clear on its own. However, the second sentence ('System operations for managing packages, system health, and updates') is a category label that adds no discriminating information, and the description never separates this from close siblings such as sm_system_clean or sm_system_clean_package_cache.

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 or when-not-to-use guidance, and no mention of when to prefer sm_system_clean or sm_system_clean_package_cache over this temp-file cleanup. The agent must infer the intended scenario entirely.

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