Skip to main content
Glama
eva-wanxin-git

Windows Automation MCP Server

get_system_info

Retrieve Windows system information including hardware specifications, OS details, and performance metrics for monitoring and automation tasks.

Instructions

获取系统信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for 'get_system_info' that executes PowerShell commands to gather system details including OS, computer model, memory, and CPU information, parses the JSON output, and returns it in a success/error structure.
    async getSystemInfo() {
      try {
        const command = `
          $os = Get-CimInstance Win32_OperatingSystem
          $cs = Get-CimInstance Win32_ComputerSystem
          $cpu = Get-CimInstance Win32_Processor
          @{
            ComputerName = $cs.Name
            OS = $os.Caption
            Version = $os.Version
            Architecture = $os.OSArchitecture
            Manufacturer = $cs.Manufacturer
            Model = $cs.Model
            TotalMemoryGB = [math]::Round($cs.TotalPhysicalMemory / 1GB, 2)
            CPU = $cpu.Name
            CPUCores = $cpu.NumberOfCores
            CPULogical = $cpu.NumberOfLogicalProcessors
          } | ConvertTo-Json
        `;
    
        const { stdout } = await execAsync(`powershell -Command "${command.replace(/"/g, '\\"')}"`, {
          shell: 'powershell.exe'
        });
    
        const info = JSON.parse(stdout);
        return { success: true, info };
      } catch (error) {
        return { success: false, error: error.message };
      }
    }
  • Tool schema definition including name, description, and empty input schema (no parameters required).
    {
      name: 'get_system_info',
      description: '获取系统信息',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Registration and dispatch logic in the executeTool switch statement that routes calls to the getSystemInfo handler.
    case 'get_system_info':
      return await this.getSystemInfo();
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. '获取系统信息' implies a read-only operation, but it doesn't specify what information is returned (e.g., OS version, hardware details, uptime), whether it requires permissions, or if there are rate limits. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 phrase '获取系统信息', which is extremely concise and front-loaded with the core purpose. There's no wasted space or unnecessary elaboration, making it efficient for quick understanding.

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 tool's complexity (simple read operation) but lack of annotations and output schema, the description is incomplete. It doesn't explain what system information is retrieved, the return format, or how it differs from sibling tools. For a tool in a server with many specific system-info siblings, more context is needed to guide proper usage.

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, and schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate. No additional parameter information is required or provided.

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 system information) states a clear verb and resource, but it's vague about what specific system information is retrieved. It doesn't distinguish from siblings like get_disk_info, get_network_info, or get_process_info, which all get specific types of system information. The purpose is understandable but lacks specificity.

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. With siblings like get_disk_info, get_network_info, and get_process_info that retrieve specific system data, the description doesn't indicate whether this tool provides a comprehensive overview, a subset, or something different. There's no mention of prerequisites, context, 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/eva-wanxin-git/windows-automation-mcp'

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