Skip to main content
Glama
Systems Manager

Systems Manager

Install Node

sm_advanced_install_node
Destructive

Installs Node.js on remote systems and optionally sets the version, using explicit confirmation for changes during host setup or orchestration.

Instructions

Install node (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_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for a mutating action. Pass true when the client cannot answer an approval prompt.
versionNoVersion of python/node

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, which is a lot of signal. The description adds nothing on top: it does not say the tool downloads from the network, whether an existing version is overwritten, or why the confirm parameter matters for a mutating action. For a destructive install tool, this is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is very short and the operation name is front-loaded. The second clause is filler that does not earn its place, but there is no bloat or buried information.

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?

This is a destructive, open-world mutation with no output schema and no annotation-contradicting detail to correct. The description leaves the agent without the essentials: what exactly gets installed or overwritten, whether network access is required, and how confirmation is handled — the schema carries nearly all of the load.

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 `confirm` and `version` are already documented in the schema, establishing the baseline of 3. The description contributes no additional meaning about version format, supported ranges, or what happens when version is null (default/latest).

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 names a specific verb and resource ("Install node") and the parenthetical identifies membership in sm_advanced_operations. However, it never disambiguates from closely-named siblings such as sm_advanced_use_node, sm_advanced_install_nvm or sm_advanced_install_package, and does not clarify whether "node" means the Node.js runtime or some other node entity — the agent must infer this from context.

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 such as installing via nvm or switching versions with sm_advanced_use_node. The trailing phrase "Operations for SSH and specialized managers" is generic family boilerplate that gives the agent nothing actionable for selection.

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