Skip to main content
Glama
Systems Manager

Systems Manager

Install Uv

sm_advanced_install_uv
Destructive

Installs the uv package manager on a managed host and uses explicit confirmation for the mutating installation action.

Instructions

Install uv (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_uv"
  }
}

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.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, so the safety profile is known. The description adds no context beyond that — it never says what is modified on the system, that a network download occurs, or how the 'confirm' approval flow behaves, and the SSH/manager sentence is irrelevant noise.

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 ('Operations for SSH and specialized managers') earns no place — it neither explains the install nor relates to the confirm parameter, and reads as boilerplate leakage.

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 installer with no output schema, an agent needs to know what gets installed, where it lands, and whether existing installs are affected. None of that is present, and the only real content duplicates the tool title.

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% and the single 'confirm' parameter is well documented in the schema itself, so the baseline of 3 applies. The description contributes nothing further about when 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 verb+resource ('Install uv') is identifiable, but 'uv' is never expanded or explained, and the trailing clause 'Operations for SSH and specialized managers' describes something else entirely, muddying rather than sharpening the purpose. Nothing distinguishes it from sm_advanced_install_node or sm_advanced_install_package beyond the tool name itself.

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 guidance on when to use this tool, no prerequisites (network access, existing Python environment), and no mention of the sibling installers as alternatives. The agent must infer everything from the name.

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