Skip to main content
Glama

getSystemInfo

Retrieve system information such as OS details, CPU architecture, memory usage, and network interfaces for monitoring and diagnostics.

Instructions

Get system information using Node.js os module

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that gathers system information (platform, architecture, CPU count, memory, uptime, Node version) using Node.js 'os' module and returns it as formatted JSON.
    handler: async () => {
      const info: SystemInfo = {
        platform: os.platform(),
        arch: os.arch(),
        cpus: os.cpus().length,
        totalMemory: os.totalmem(),
        freeMemory: os.freemem(),
        uptime: os.uptime(),
        nodeVersion: process.version
      };
    
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(info, null, 2)
        }]
      };
    }
  • TypeScript interface defining the structure of the system information returned by the getSystemInfo tool.
    export interface SystemInfo {
      platform: string;
      arch: string;
      cpus: number;
      totalMemory: number;
      freeMemory: number;
      uptime: number;
      nodeVersion: string;
    }
  • src/index.ts:28-35 (registration)
    Registration of all tools including systemTools (which contains getSystemInfo) into the allTools object used by the MCP server handlers for listing and execution.
    const allTools: ToolKit = {
      ...systemTools,
      ...networkTools,
      ...geoTools,
      ...generatorTools,
      ...dateTimeTools,
      ...securityTools
    };
  • Definition and export of the getSystemInfo tool within the systemTools object, including name, description, input schema, and handler.
    getSystemInfo: {
      name: 'getSystemInfo',
      description: 'Get system information using Node.js os module',
      inputSchema: {
        type: 'object',
        properties: {}
      },
      handler: async () => {
        const info: SystemInfo = {
          platform: os.platform(),
          arch: os.arch(),
          cpus: os.cpus().length,
          totalMemory: os.totalmem(),
          freeMemory: os.freemem(),
          uptime: os.uptime(),
          nodeVersion: process.version
        };
    
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(info, null, 2)
          }]
        };
      }
    },
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 states the tool retrieves information (implying read-only), but doesn't specify what system information is included, whether it requires permissions, potential rate limits, or error conditions. This leaves significant gaps for a tool that interacts with system resources.

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 perfectly concise - a single sentence that directly states the tool's purpose and implementation method with zero wasted words. It's front-loaded with the core functionality and doesn't include unnecessary elaboration.

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?

For a system information tool with no annotations and no output schema, the description is insufficient. It doesn't explain what information is returned, the format of the response, or how this differs from similar sibling tools. Given the complexity of system information and lack of structured documentation, more context is needed.

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 zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't waste space discussing parameters that don't exist, earning a baseline score of 4 for parameter semantics.

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 action ('Get system information') and implementation method ('using Node.js os module'), which distinguishes it from siblings like getLoadAverage or getNetworkInterfaces that provide specific subsets of system data. However, it doesn't explicitly differentiate itself from all possible sibling tools that might also retrieve system information.

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 like getLoadAverage, getNetworkInterfaces, or getCurrentTime. There's no mention of what specific information is returned, prerequisites, or typical use cases, leaving the agent with minimal context for selection.

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/cyanheads/toolkit-mcp-server'

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