Skip to main content
Glama

get_system_info

Retrieve basic system information from the mcp-flyin server to monitor hardware and software status for troubleshooting and management.

Instructions

Get basic system information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_system_info' tool. It dynamically imports the Node.js 'os' module, gathers system information (platform, architecture, Node version, uptime, total and free memory), and returns it as a formatted JSON string in a text content block.
    case 'get_system_info':
      const os = await import('os');
      const systemInfo = {
        platform: os.platform(),
        arch: os.arch(),
        nodeVersion: process.version,
        uptime: os.uptime(),
        totalMemory: os.totalmem(),
        freeMemory: os.freemem(),
      };
      
      return {
        content: [
          {
            type: 'text',
            text: `System Information:\n${JSON.stringify(systemInfo, null, 2)}`,
          },
        ],
      };
  • server.js:67-74 (registration)
    Registration of the 'get_system_info' tool in the ListTools handler, providing the tool name, description, and empty input schema (no parameters required).
    {
      name: 'get_system_info',
      description: 'Get basic system information',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • The input schema for 'get_system_info' tool, defined as an empty object (no input parameters).
    {
      name: 'get_system_info',
      description: 'Get basic system information',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
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. 'Get basic system information' implies a read operation but provides no details about what information is returned, format, permissions required, rate limits, or error conditions. 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 extremely concise - a single four-word phrase that directly states the tool's purpose. There's zero wasted language, and the information is front-loaded appropriately. This is an excellent example of efficient communication.

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, no output schema, and a tool that presumably returns system information, the description is insufficient. 'Basic system information' is vague - it doesn't indicate what information is included (CPU, memory, OS, etc.) or the return format. The agent needs more context to understand what to expect from this tool.

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. The description appropriately doesn't discuss parameters since none exist. This matches the baseline expectation for parameterless tools, though it doesn't add any value beyond what the schema already indicates.

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 basic system information' clearly states the verb ('Get') and resource ('basic system information'), providing a general purpose. However, it doesn't differentiate from sibling tools like 'calculate' or 'echo' - it's clear what it does but not how it differs from alternatives. The purpose is understandable but lacks sibling distinction.

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 the sibling tools 'calculate' or 'echo'. There's no mention of appropriate contexts, prerequisites, or alternatives. The agent receives no help in choosing between available tools on this server.

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/balajidommeti/MCP'

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