Skip to main content
Glama
Systems Manager

Systems Manager

Install Applications

sm_system_install_applications
Destructive

Installs specified applications or packages on a system and uses a confirmation flag to approve the mutating change.

Instructions

Install applications (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_install_applications"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
packagesNoList of applications/packages

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?

The annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false and readOnlyHint=false; the description adds nothing beyond that, repeating only generic category language. It does not say what installation entails (source of packages, network access, whether existing versions are replaced, side effects of failure), which matters for a destructive mutation.

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 definition is short, but the second sentence is category filler that does not describe this tool, and the "(sm_system_operations)" tag adds no actionable information. Only the first three words actually earn their 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?

For a destructive, non-idempotent install operation in a crowded family of install tools, the description does not explain scope, source, or selection criteria relative to alternatives. The annotations cover the safety profile, but the ambiguity between install siblings is left unresolved.

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?

Schema description coverage is 100%, so both parameters (packages and confirm) are already documented in the schema, establishing a baseline of 3. The description adds no additional meaning about package formats, accepted identifiers, or when explicit confirmation is required.

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 description states a concrete verb and resource ("Install applications"), but the parenthetical group tag and the second sentence ("System operations for managing packages, system health, and updates") are category boilerplate rather than tool-specific purpose. With siblings such as sm_system_install_local_package, sm_system_install_python_modules and sm_advanced_install_package, an agent gets no basis for deciding which install tool applies here.

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, no mention of prerequisites, repositories, or the approval-prompt behavior implied by the confirm parameter. An agent must infer entirely from the name when this tool is the right choice among roughly eight install-related siblings.

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