Skip to main content
Glama
eva-wanxin-git

Windows Automation MCP Server

get_process_info

Retrieve detailed information about running Windows processes to monitor system activity, identify resource usage, and manage applications effectively.

Instructions

获取进程详细信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes进程名称

Implementation Reference

  • The handler function that executes the tool logic: queries Windows tasklist for process details, parses CSV output, and returns structured info including PID, memory, status, username, and window title.
    async getProcessInfo(processName) {
      try {
        const { stdout } = await execAsync(`tasklist /FI "IMAGENAME eq ${processName}" /FO CSV /V`);
        const lines = stdout.trim().split('\n');
        if (lines.length < 2) {
          return { success: false, message: '进程未找到' };
        }
    
        const info = lines[1].split(',').map(p => p.replace(/"/g, ''));
        return {
          success: true,
          process: {
            name: info[0],
            pid: info[1],
            session: info[2],
            memory: info[4],
            status: info[5],
            username: info[6],
            windowTitle: info[8],
          },
        };
      } catch (error) {
        return { success: false, error: error.message };
      }
    }
  • Input schema definition for the get_process_info tool, specifying required 'name' parameter as string.
      {
        name: 'get_process_info',
        description: '获取进程详细信息',
        inputSchema: {
          type: 'object',
          properties: {
            name: { type: 'string', description: '进程名称' },
          },
          required: ['name'],
        },
      },
    ];
  • Tool registration in the executeTool method's switch statement, dispatching calls to the getProcessInfo handler.
    case 'get_process_info':
      return await this.getProcessInfo(args.name);
  • Tool name listed in canHandle method for routing tool calls to this module.
    const tools = ['launch_application', 'kill_process', 'list_processes', 'get_process_info'];
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 ('获取进程详细信息') without mentioning permissions needed, output format, error handling, or system impact (e.g., whether it's read-only or has side effects). This is inadequate for a tool that likely interacts with system processes.

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 without unnecessary words. It's front-loaded and wastes no space, making it highly concise.

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 and no output schema, the description is incomplete for a tool that retrieves system process information. It lacks details on return values, error cases, or behavioral traits (e.g., read-only nature), which are critical for an AI agent to use it correctly in a system 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?

Schema description coverage is 100%, with the single parameter 'name' documented as '进程名称' (process name). The description doesn't add any meaning beyond this, such as format examples or constraints. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

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

Purpose3/5

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

The description '获取进程详细信息' (Get process details) states a clear verb ('获取' - get) and resource ('进程详细信息' - process details), providing basic purpose. However, it doesn't differentiate from sibling tools like 'list_processes' or 'kill_process', leaving ambiguity about what specific information is retrieved versus other process-related operations.

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. The description doesn't mention prerequisites, context (e.g., vs. 'list_processes' for enumeration), or exclusions, leaving the agent to infer usage from the tool name alone.

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