Skip to main content
Glama
Systems Manager

Systems Manager

Install Nvm

sm_advanced_install_nvm
Destructive

Install nvm to manage multiple Node.js versions on a target host, with explicit confirmation required before this mutating operation.

Instructions

Install nvm (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_nvm"
  }
}

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.8/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 agent knows this mutates the system and reaches the network. The description adds nothing beyond that: it never says what is written to disk, whether an existing nvm install is overwritten, whether a download occurs, or what happens on partial failure — exactly the context a destructive, non-idempotent installer needs.

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-loaded with the action, which is good. The second sentence is dead weight that neither clarifies the action nor routes to an alternative, so it does not earn its 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, network-touching install with no output schema, the description omits nearly everything an agent would need: target location, whether sudo/root is required, overwrite semantics, and success/failure signals. The annotated safety profile is the only real information available.

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 fully documented in the schema itself, including its default and the case where the client cannot answer an approval prompt. The description adds no further meaning, but with complete schema coverage the baseline of 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?

The name and title carry the specific verb+resource ('Install nvm'), and the description's opening words restate it, so the agent knows this installs the nvm version manager. However, the trailing clause 'Operations for SSH and specialized managers' is unrelated to installing nvm and muddies the purpose rather than sharpening it.

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 versus siblings such as sm_advanced_install_node or sm_advanced_use_node, nor any prerequisite or ordering advice (e.g., install nvm before selecting a Node version). The agent must infer placement in a workflow entirely.

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