Skip to main content
Glama
Systems Manager

Systems Manager

Install Package

sm_advanced_install_package
Destructive

Install a specified package on a managed system or into a virtual environment, with explicit confirmation available for mutating actions.

Instructions

Install package (sm_advanced_operations). Operations for SSH and specialized managers

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_advanced_install_package"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoPath for venv
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
packageNoPackage name to install

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, readOnlyHint=false, and idempotentHint=false, so the safety profile is partly covered. The description adds nothing beyond that: it doesn't say what gets modified (system vs. venv), whether elevated privileges are needed, whether network downloads occur, or how the destructive effect manifests. The phrase "specialized managers" is unexplained.

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 verb, but the trailing "Operations for SSH and specialized managers" is filler that neither scopes the tool nor helps the agent decide. Nothing is wasted-length-wise, but the content that is present is partly noise.

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, open-world mutation tool with three parameters and no output schema, the description should say what environment is targeted and what the confirmation flag guards against. Instead it omits the target scope entirely and never clarifies the unusual `path`/venv parameter, so an agent lacks enough context to call it safely.

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 `path`, `package`, and `confirm` are already documented in the schema, which sets the baseline at 3. The description adds no meaning about how `path` (labelled "Path for venv") relates to package installation, leaving an ambiguity that only the schema hints at.

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 gives a clear verb and resource ("Install package"), but the parenthetical "(sm_advanced_operations)" only names the tool's group, and "Operations for SSH and specialized managers" is a category label rather than a statement of what installation actually means here. It does not distinguish this from siblings such as sm_system_install_local_package, sm_advanced_install_node, sm_advanced_install_nvm, or sm_advanced_install_uv, so an agent cannot tell which installer to pick.

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 mention of alternatives despite several sibling tools that also install software (local package, node, nvm, uv, python modules). The agent must infer scope from the name 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