Skip to main content
Glama
qckfx

Node.js Debugger MCP Server

by qckfx

list_processes

View all active Node.js processes managed by the debugger server to monitor and control debugging sessions.

Instructions

List all managed Node.js processes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that lists all managed Node.js processes, returning their pid, port, command, startTime, and status as JSON.
    private async listProcesses() {
      const processes = Array.from(this.managedProcesses.values()).map(p => ({
        pid: p.pid,
        port: p.port,
        command: `${p.command} ${p.args.join(" ")}`,
        startTime: p.startTime.toISOString(),
        status: p.process.killed ? 'killed' : 'running'
      }));
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(processes, null, 2),
          },
        ],
      };
    }
  • Tool schema definition in ListToolsRequestSchema, specifying the name, description, and empty input schema (no parameters required).
    {
      name: "list_processes",
      description: "List all managed Node.js processes",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:250-252 (registration)
    Registration in the CallToolRequestSchema handler switch statement, which calls the listProcesses method when the tool is invoked.
    case "list_processes":
      return await this.listProcesses();
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but doesn't reveal any behavioral traits, such as whether it requires specific permissions, how it handles errors, if it's read-only or has side effects, or what the output format might be. This leaves significant gaps in understanding the tool's behavior.

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, clear sentence that directly states the tool's purpose without any fluff or redundant information. It's front-loaded and efficiently communicates the essential action, making it easy to parse and understand quickly.

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?

Given the lack of annotations and output schema, the description is incomplete for a tool that likely returns a list of processes. It doesn't explain what 'managed' means, the format of the output (e.g., list of IDs, names, statuses), or any limitations like pagination. For a tool with no structured data to rely on, this leaves too much unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. This meets the baseline for tools with no parameters, as it avoids unnecessary details.

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 description clearly states the verb ('List') and resource ('all managed Node.js processes'), making the purpose immediately understandable. However, it doesn't differentiate from potential sibling tools like 'attach_debugger' or 'kill_process' beyond the basic operation type, which would require more specific scope or context information.

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 provides no guidance on when to use this tool versus alternatives like 'start_node_process' or 'kill_process'. It lacks context about prerequisites, such as whether processes must be running or managed, and doesn't mention any exclusions or specific scenarios for its use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/qckfx/node-debugger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server