Skip to main content
Glama
Systems Manager

Systems Manager

Update

sm_system_update
Destructive

Updates system packages and health on managed hosts, using explicit confirmation to control mutating actions.

Instructions

Update (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_update"
  }
}

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, openWorldHint=true, idempotentHint=false and readOnlyHint=false, which is the important safety signal. The description adds nothing on top of that: it does not say what gets modified or destroyed, whether a reboot is needed, whether it applies to all packages or a subset, or how long/failure-prone the operation is.

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-loaded, but the second sentence is generic category filler that conveys no operational information, and the parenthetical repeats the tool name rather than adding scope detail.

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 and no documented return values, the description leaves essential questions unanswered: what exactly is updated, what are the prerequisites, and what state the system is left in. It is not adequate for the risk profile the annotations advertise.

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 with 100% schema description coverage, and the schema fully explains the confirm flag. The description contributes no additional meaning about when confirmation is expected, so the baseline of 3 applies.

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 is effectively the name restated: "Update" plus a category label "System operations for managing packages, system health, and updates." It never says what is actually updated (installed packages? OS? all upgradable packages?) or the scope of the operation, so an agent cannot distinguish it from siblings like sm_system_list_upgradable_packages or sm_system_install_local_package.

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 named alternative or condition for choosing this tool over package-list or install tools. The parenthetical reference to sm_system_operations does not establish any selection criteria.

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