Skip to main content
Glama

list_processes

View all active terminal processes managed by the MCP Terminal server to monitor system activity and manage running applications.

Instructions

List all running processes managed by this MCP server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The implementation of the `listProcesses` method in `ProcessManager` which retrieves and formats the list of running processes.
    async listProcesses(): Promise<{ processes: { id: string; status: "running"; command: string; logFile: string }[] }> {
      const processes: { id: string; status: "running"; command: string; logFile: string }[] = [];
    
      for (const [id, processInfo] of this.processes) {
        // Get command from spawn arguments (stored in process.spawnargs)
        const command = processInfo.process.spawnargs?.join(' ') || '';
    
        processes.push({
          id,
          status: 'running',
          command,
          logFile: processInfo.logFile,
        });
      }
    
      return { processes };
    }
  • src/index.ts:77-84 (registration)
    Registration of the `list_processes` tool in the MCP server definition.
    {
      name: 'list_processes',
      description: 'List all running processes managed by this MCP server',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Request handler logic in `src/index.ts` that maps the MCP tool call `list_processes` to the `processManager.listProcesses()` method.
    case 'list_processes': {
      const result = await processManager.listProcesses();
      return { content: [{ type: 'text', text: JSON.stringify(result) }] };
    }
  • Type definition for the output of the `list_processes` tool.
    export interface ListProcessesOutput {
      processes: {
        id: string;
        status: "running";
        command: string;
        logFile: string;
      }[];
    }
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 the action ('List all running processes') but lacks details on permissions, rate limits, output format, or whether it's a safe read operation. This is insufficient for a tool with no annotation coverage.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured.

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?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic action but lacks details on behavior and output, which are important for completeness even in simple tools.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter information, and it appropriately doesn't mention any, earning a baseline score near the top of the scale.

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 ('running processes managed by this MCP server'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_logs' or 'search_logs', which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_logs' or 'search_logs'. The description implies usage for listing processes but offers no context on prerequisites, timing, or exclusions.

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/h004888/mcp_terminal_process'

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