Skip to main content
Glama
Systems Manager

Systems Manager

Optimize

sm_system_optimize
Destructive

Manage packages, assess system health, and apply updates to improve system operations. Set confirm to authorize mutating actions when approval prompts are unavailable.

Instructions

Optimize (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_optimize"
  }
}

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

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

Annotations declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the risk profile is known, but the description adds nothing about what gets destroyed, whether changes are reversible, or what permissions or downtime are required. For a non-idempotent destructive system operation, silence on scope and reversibility is a meaningful gap even under the lowered bar annotations set.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is two short fragments with no padding, so it is structurally tight. The brevity is under-specification rather than elegance, but nothing in the text is redundant verbosity.

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, open-world system mutation with no output schema, the description should convey what is optimized, the expected effect, and risk. It conveys only a generic category phrase, leaving the agent unable to predict consequences before invoking it.

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 and schema coverage is 100%, with the schema fully explaining that confirm=true is for clients that cannot answer an approval prompt, so per the coverage baseline a 3 applies. The description adds no context about what confirming actually triggers, which is unfortunate given the destructive annotation, but it does not detract from the schema.

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?

The description restates the title ("Optimize") and follows it with a category blurb ("System operations for managing packages, system health, and updates") that could be pasted onto any of the dozen-plus sm_system_* siblings. It never says what is actually optimized, what the operation changes, or how it differs from siblings like sm_system_clean or sm_system_update.

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 routing to alternatives, despite a sibling set that includes sm_system_clean, sm_system_clean_temp_files, sm_system_clean_package_cache, and sm_system_update. An agent has no way to decide between this tool and those from the definition alone.

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