Skip to main content
Glama
Sign In
nodejs-repl-mcp

nodejs-repl-mcp

by unfallenwill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Install npm packages into session

install_packages

Install npm packages into a target Node.js REPL session so later exec calls can require or import them.

Instructions

Run npm install in the session workspace so subsequent exec calls can require/import the packages. Installs into that session only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "packages": "<packages>"
    },
    "name": "install_packages"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesTarget session name
saveDevNoSave as devDependencies
packagesYesPackage specifiers, e.g. ["lodash@^4"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal that the operation only affects that session and that packages become available to subsequent exec calls. However, it does not mention side effects like modifying package.json, network requirements, or the need for package-lock updates, which an agent might need to predict outcomes.

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?

Two sentences with no filler. The core command, its purpose, and the session-isolation behavior are all presented efficiently, with the most important information front-loaded.

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

Completeness4/5

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

For a three-parameter tool with no output schema and no annotations, the description covers the core invocation, purpose, and scope. Minor gaps remain around expected output/errors and whether this modifies package manifests, but the essentials for correct invocation are present.

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 the schema already documents all three parameters clearly. The description adds no parameter-specific meaning beyond what is in the schema, matching the baseline of 3.

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 states a specific action ('Run `npm install`'), a target resource ('in the session workspace'), and the intended outcome ('subsequent exec calls can require/import the packages'). It is clearly differentiated from siblings like create_session, exec, and remove_session by focusing on package installation into an existing session.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: use this to install packages so later exec calls can import them. It does not explicitly list when not to use it or name alternatives such as exec for running commands directly, so it falls just short of full usage-guideline coverage.

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