Skip to main content
Glama
Systems Manager

Systems Manager

Install Local Package

sm_system_install_local_package
Destructive

Install a local package file on the system to deploy software updates or applications. Use when a package is available locally and needs installation through Systems Manager.

Instructions

Install local package (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_local_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
file_pathNoPath to local package file

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, openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is mostly covered. The description adds nothing beyond that: it does not say whether the install requires elevation, whether it can overwrite an existing version, or what happens on failure — the kind of detail that 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?

It is short and front-loads the action, but the second sentence is filler that conveys nothing the tool name does not. Every sentence should earn its place, and this one does not.

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 with no output schema, the description should say what state changes occur and what the result reports. It leaves all of that to annotations and the caller's assumptions.

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%, with both confirm and file_path documented in the schema, so baseline is 3. The description contributes no additional meaning about accepted file formats, path conventions, or the approval flow implied by confirm.

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 name and first clause state a concrete verb+resource ('Install local package'), which is clear enough on its own. But the definition makes no attempt to distinguish it from near-siblings such as sm_advanced_install_package or sm_system_install_applications, so an agent cannot tell which installer applies without opening both schemas.

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 prerequisites, and no reference to the advanced/local-package alternative. The second sentence ('System operations for managing packages, system health, and updates') is a category blurb, not usage guidance.

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