Skip to main content
Glama
Systems Manager

Systems Manager

Install Python Modules

sm_system_install_python_modules
Destructive

Install Python modules on managed systems by specifying package names to add required dependencies and support application setup.

Instructions

Install python modules (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_python_modules"
  }
}

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

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, and readOnlyHint=false, so the agent knows this is a mutating, network-touching, non-repeatable operation. The description adds no context beyond that — nothing about whether existing versions are overwritten, what permissions are needed, or how conflicts with the system package manager are handled. It does not contradict the annotations.

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 first clause is front-loaded and efficient. The second sentence is filler that could describe any tool in this server, and the parenthetical tool-id restates metadata already carried by the name and title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, fully-schema-documented mutation tool with rich annotations and no output schema, the structured fields cover most of what an agent needs. The gap is behavioral and selection context — when to pick this over the many sibling installers, and what the install actually affects — which the description leaves entirely unaddressed.

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 `packages` (list of applications/packages) and `confirm` (explicit confirmation for a mutating action) are already documented in the schema. The description adds nothing about install target, version pinning, or interpreter selection, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Install python modules" states a specific verb and resource, so the core operation is unambiguous. However, the parenthetical "(sm_system_operations)" and the trailing "System operations for managing packages, system health, and updates" are generic boilerplate that do nothing to distinguish this from sm_advanced_install_package, sm_advanced_install_uv, or sm_system_install_applications.

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?

The description gives no when-to-use guidance and no alternatives. It never says how this differs from the sibling installers (system package manager, uv, node/nvm) or when a Python-module install is the right choice over them, and it says nothing about prerequisites such as an available Python interpreter.

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