Skip to main content
Glama
Sign In
dev-env-setup

dev-env-setup

by cmwen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

install_nodejs

Install a specified Node.js version on macOS or Linux using nvm or the package manager. Accepts a version like '20' or '18', or defaults to LTS.

Instructions

Install Node.js via nvm or package manager

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": "install_nodejs"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionNoNode.js version to install (e.g., "lts", "20", "18")lts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden. It only mentions 'via nvm or package manager' without disclosing system modifications, required permissions, idempotency, or impact on the environment. For a mutation tool, this is insufficient transparency.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no filler. Every word contributes to meaning, making it appropriately concise for a simple tool with one optional parameter.

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 simple tool with one optional param and no output schema, the description is minimally adequate. However, it lacks context about prerequisites (e.g., nvm installation) and does not explain how this tool fits with sibling tools like install_package_manager or install_multiple, limiting completeness.

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?

The schema fully documents the single 'version' parameter with default and examples (100% coverage), so the description need not add more. The tool description adds no parameter-specific meaning beyond what the schema already provides, which matches the baseline.

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

Purpose5/5

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

The description clearly states the verb 'Install' and the resource 'Node.js', and specifies the method 'via nvm or package manager'. This distinguishes it from sibling tools like install_python, install_flutter, and install_android which target different runtimes.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or relationships to sibling tools like install_multiple or install_package_manager, leaving the agent without decision support.

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