Skip to main content
Glama

system_info

Retrieve Windows system information including hardware details, OS configuration, environment variables, and installed software for system analysis and troubleshooting.

Instructions

Comprehensive system information including hardware details, OS info, environment variables, and system configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesThe system information action to perform
categoryNoHardware category to focus on (for hardware_info action)all
filterNoFilter for environment variables or software (supports wildcards)

Implementation Reference

  • The main handler function for the 'system_info' tool. It takes input parameters and dispatches to specific helper methods based on the 'action' parameter.
    async run(args: {
      action: string;
      category?: string;
      filter?: string;
    }) {
      try {
        switch (args.action) {
          case "get_system_overview":
            return await this.getSystemOverview();
          case "get_hardware_info":
            return await this.getHardwareInfo(args.category);
          case "get_os_info":
            return await this.getOSInfo();
          case "get_environment_vars":
            return await this.getEnvironmentVars(args.filter);
          case "get_installed_software":
            return await this.getInstalledSoftware(args.filter);
          case "get_system_uptime":
            return await this.getSystemUptime();
          case "get_user_info":
            return await this.getUserInfo();
          case "get_system_paths":
            return await this.getSystemPaths();
          default:
            throw new Error(`Unknown action: ${args.action}`);
        }
      } catch (error: any) {
        return {
          content: [{
            type: "text",
            text: `❌ System information operation failed: ${error.message}`
          }],
          isError: true
        };
      }
    },
  • Input schema defining the parameters for the 'system_info' tool, including required 'action' and optional 'category' and 'filter'.
    parameters: {
      type: "object",
      properties: {
        action: {
          type: "string",
          enum: ["get_system_overview", "get_hardware_info", "get_os_info", "get_environment_vars", "get_installed_software", "get_system_uptime", "get_user_info", "get_system_paths"],
          description: "The system information action to perform"
        },
        category: {
          type: "string",
          enum: ["cpu", "memory", "disk", "network", "all"],
          description: "Hardware category to focus on (for hardware_info action)",
          default: "all"
        },
        filter: {
          type: "string",
          description: "Filter for environment variables or software (supports wildcards)"
        }
      },
      required: ["action"]
    },
  • src/index.ts:38-41 (registration)
    Registration of the 'system_info' tool in the MCP server's listTools handler, providing name, description, and input schema.
      name: systemInfoTool.name,
      description: systemInfoTool.description,
      inputSchema: systemInfoTool.parameters
    },
  • src/index.ts:75-76 (registration)
    Tool call dispatching in the MCP server's callTool handler, invoking systemInfoTool.run() for 'system_info' requests.
    case "system_info":
      return await systemInfoTool.run(args as any);
  • Helper method for 'get_system_overview' action, gathering basic system info using Node.js os module and PowerShell.
    async getSystemOverview() {
      try {
        const nodeInfo = {
          platform: os.platform(),
          arch: os.arch(),
          hostname: os.hostname(),
          totalMemory: this.formatBytes(os.totalmem()),
          freeMemory: this.formatBytes(os.freemem()),
          cpuCount: os.cpus().length,
          uptime: this.formatUptime(os.uptime())
        };
    
        const command = `Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, TotalPhysicalMemory, CsProcessors, CsSystemType, TimeZone | Format-List`;
        const { stdout } = await execAsync(`powershell -Command "${command}"`);
    
        const result = `# System Overview\n\n## Basic Information\n` +
          `- **Hostname**: ${nodeInfo.hostname}\n` +
          `- **Platform**: ${nodeInfo.platform}\n` +
          `- **Architecture**: ${nodeInfo.arch}\n` +
          `- **CPU Cores**: ${nodeInfo.cpuCount}\n` +
          `- **Total Memory**: ${nodeInfo.totalMemory}\n` +
          `- **Free Memory**: ${nodeInfo.freeMemory}\n` +
          `- **System Uptime**: ${nodeInfo.uptime}\n\n` +
          `## Windows Details\n\`\`\`\n${stdout}\n\`\`\``;
    
        return {
          content: [{ type: "text", text: result }]
        };
      } catch (error: any) {
        throw new Error(`Failed to get system overview: ${error.message}`);
      }
    },
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. It states what information is retrieved but doesn't mention whether this requires admin permissions, if it's read-only (implied but not stated), potential performance impacts, or output format details. For a system information tool with zero annotation coverage, this is insufficient.

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, well-structured sentence that efficiently lists the key information categories. It's front-loaded with the main purpose and avoids unnecessary words, making it easy to scan 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 complexity of a system information tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects like permissions or performance, provide usage guidance relative to siblings, or detail output structure. For a tool that could expose sensitive system data, more context is needed.

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 lists categories of information (hardware, OS, environment variables, configuration) which partially map to the 'action' parameter's enum values. However, with 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds marginal value by providing high-level context but doesn't explain parameter interactions or usage beyond what the schema provides.

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 tool's purpose: retrieving comprehensive system information with specific categories listed (hardware details, OS info, environment variables, system configuration). It uses a specific verb ('including') and identifies the resource ('system information'), though it doesn't explicitly differentiate from sibling tools like 'performance' or 'process_manager'.

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. It doesn't mention sibling tools or specify scenarios where this tool is preferred over others like 'performance' for metrics or 'process_manager' for process-related information. Usage context is implied but not explicit.

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/guangxiangdebizi/windows-system-mcp'

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