Skip to main content
Glama
eva-wanxin-git

Windows Automation MCP Server

list_processes

Lists running Windows processes to monitor system activity, identify resource usage, and manage applications. Use optional filters to find specific processes by name.

Instructions

列出正在运行的进程

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filterNo过滤进程名(可选)

Implementation Reference

  • The handler function for list_processes tool. Executes 'tasklist' command to list processes, parses CSV output, applies optional filter, and returns the list with success status.
    async listProcesses(filter = '') {
      try {
        const { stdout } = await execAsync('tasklist /FO CSV /NH');
        const lines = stdout.trim().split('\n');
        const processes = lines.map(line => {
          const parts = line.split(',').map(p => p.replace(/"/g, ''));
          return {
            name: parts[0],
            pid: parts[1],
            memory: parts[4],
          };
        });
    
        const filtered = filter 
          ? processes.filter(p => p.name.toLowerCase().includes(filter.toLowerCase()))
          : processes;
    
        return { success: true, processes: filtered, count: filtered.length };
      } catch (error) {
        return { success: false, error: error.message };
      }
    }
  • Schema definition for the list_processes tool, including name, description, and input schema allowing optional filter string.
    {
      name: 'list_processes',
      description: '列出正在运行的进程',
      inputSchema: {
        type: 'object',
        properties: {
          filter: { type: 'string', description: '过滤进程名(可选)' },
        },
      },
    },
  • Registration and dispatch logic in the executeTool method's switch statement, routing 'list_processes' calls to the listProcesses handler.
    case 'list_processes':
      return await this.listProcesses(args.filter);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does ('列出正在运行的进程') but doesn't describe what information is returned, format of output, whether it's real-time or cached data, permissions needed, or any side effects. This is inadequate 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 phrase that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple listing tool and gets straight to the point.

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 no annotations, no output schema, and a description that only states the basic purpose, this is incomplete. For a process listing tool, the description should ideally mention what information is returned (PID, name, CPU usage, etc.), format considerations, or any limitations. The current description is too minimal given the context.

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 description doesn't mention parameters at all, but the input schema has 100% description coverage with the 'filter' parameter documented as '过滤进程名(可选)' (filter process name, optional). Since schema coverage is high, the baseline is 3 even without parameter information in the description.

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 '列出正在运行的进程' (List running processes) clearly states the verb ('列出' - list) and resource ('正在运行的进程' - running processes). It's specific about what it does, though it doesn't explicitly distinguish from the sibling 'get_process_info' tool, which might provide different information about processes.

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. There's no mention of when to use it instead of 'get_process_info' or other sibling tools, nor any context about prerequisites or typical use cases.

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/eva-wanxin-git/windows-automation-mcp'

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