Skip to main content
Glama
p-united
by p-united

get_system_info

Retrieve system information such as hardware specs, OS details, and performance metrics to monitor device status and troubleshoot issues.

Instructions

システム情報を取得します

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'get_system_info' tool. It collects various system metrics using Node.js 'os' module including platform, architecture, OS release, hostname, uptime (in hours), total/free memory (in GB), CPU count, home directory, and temp directory. Formats the info as JSON and returns it wrapped in CallToolResult with text content.
    private async getSystemInfo(): Promise<CallToolResult> {
      console.error("Getting system info");
      const info = {
        platform: os.platform(),
        arch: os.arch(),
        release: os.release(),
        hostname: os.hostname(),
        uptime: `${Math.floor(os.uptime() / 3600)}時間`,
        memory: {
          total: `${Math.round(os.totalmem() / 1024 / 1024 / 1024)}GB`,
          free: `${Math.round(os.freemem() / 1024 / 1024 / 1024)}GB`,
        },
        cpus: os.cpus().length,
        homeDir: os.homedir(),
        tmpDir: os.tmpdir(),
      };
    
      return {
        content: [
          {
            type: "text",
            text: `システム情報:\n\n${JSON.stringify(info, null, 2)}`,
          },
        ],
        isError: false,
      };
    }
  • src/index.ts:161-168 (registration)
    Registration of the 'get_system_info' tool in the TOOLS constant array used by ListToolsRequestSchema handler. Defines the tool name, Japanese description ('Obtains system information'), and empty inputSchema (no parameters required).
    {
      name: "get_system_info",
      description: "システム情報を取得します",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • src/index.ts:287-288 (registration)
    Dispatch/registration logic in the switch statement of CallToolRequestSchema handler. Routes calls to 'get_system_info' by invoking the private getSystemInfo() method.
    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. The description only states what the tool does ('get system information') without revealing any behavioral traits such as what specific information is returned, whether it requires special permissions, if there are rate limits, or how the information is formatted. This leaves significant gaps for a tool with zero 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 in Japanese that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple, parameterless tool and is front-loaded with the essential information.

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 simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but has clear gaps. It states what the tool does but doesn't explain what 'system information' includes, the return format, or any behavioral context. For a tool with no annotations or output schema, more detail would be helpful to understand what to expect from the operation.

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 parameters. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters. The baseline for 0 parameters with high schema coverage is 4.

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 purpose as 'get system information' with a specific verb ('取得します' - get/retrieve) and resource ('システム情報' - system information). It distinguishes from siblings like file operations (create_sample_file, read_file) but doesn't explicitly differentiate from get_allowed_paths which also retrieves system-related data.

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 are no explicit when/when-not instructions, no mention of prerequisites, and no comparison to sibling tools like get_allowed_paths that might retrieve related system data.

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/p-united/mcpSample'

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