Skip to main content
Glama
allenbijo

MCP System Info Server

get_sysinfo

Retrieve real-time system information including CPU, memory, disk, and processor details for monitoring and diagnostic purposes.

Instructions

Get the current system information. Gives system information such as System, Node name, Release, Version, Machine, Processor CPU Information such as Processor, Physical Cores, Logical Cores Memory Information such as Total Memory, Available Memory, Used Memory, Memory Utilization Disk Information such as Total Disk Space, Used Disk Space, Free Disk Space, Disk Space Utilization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • sysinfo.py:9-18 (handler)
    The tool handler function for 'get_sysinfo', decorated with @mcp.tool() for registration, fetches system info asynchronously and returns it as a formatted string.
    @mcp.tool()
    async def get_sysinfo() -> str:
        """Get the current system information.
        Gives system information such as System, Node name, Release, Version, Machine, Processor
        CPU Information such as Processor, Physical Cores, Logical Cores
        Memory Information such as Total Memory, Available Memory, Used Memory, Memory Utilization
        Disk Information such as Total Disk Space, Used Disk Space, Free Disk Space, Disk Space Utilization
        """
        data = await get_system_info()
        return data
  • Supporting utility function that gathers comprehensive system information (CPU, memory, disk) using platform and psutil libraries, formats it into a multi-line string, and returns it. Called by the tool handler.
    async def get_system_info():
        output = []
    
        system_info = platform.uname()
        output.append("System Information:")
        output.append(f"System: {system_info.system}")
        output.append(f"Node Name: {system_info.node}")
        output.append(f"Release: {system_info.release}")
        output.append(f"Version: {system_info.version}")
        output.append(f"Machine: {system_info.machine}")
        output.append(f"Processor: {system_info.processor}")
    
        cpu_info = platform.processor()
        cpu_count = psutil.cpu_count(logical=False)
        logical_cpu_count = psutil.cpu_count(logical=True)
    
        output.append("\nCPU Information:")
        output.append(f"Processor: {cpu_info}")
        output.append(f"Physical Cores: {cpu_count}")
        output.append(f"Logical Cores: {logical_cpu_count}")
    
        memory_info = psutil.virtual_memory()
    
        output.append("\nMemory Information:")
        output.append(f"Total Memory: {memory_info.total} bytes")
        output.append(f"Available Memory: {memory_info.available} bytes")
        output.append(f"Used Memory: {memory_info.used} bytes")
        output.append(f"Memory Utilization: {memory_info.percent}%")
    
        disk_info = psutil.disk_usage('/')
    
        output.append("\nDisk Information:")
        output.append(f"Total Disk Space: {disk_info.total} bytes")
        output.append(f"Used Disk Space: {disk_info.used} bytes")
        output.append(f"Free Disk Space: {disk_info.free} bytes")
        output.append(f"Disk Space Utilization: {disk_info.percent}%")
    
        # gpus = GPUtil.getGPUs()
    
        # if not gpus:
        #     output.append("No GPU detected.")
        # else:
        #     for i, gpu in enumerate(gpus):
        #         output.append(f"\nGPU {i + 1} Information:")
        #         output.append(f"ID: {gpu.id}")
        #         output.append(f"Name: {gpu.name}")
        #         output.append(f"Driver: {gpu.driver}")
        #         output.append(f"GPU Memory Total: {gpu.memoryTotal} MB")
        #         output.append(f"GPU Memory Free: {gpu.memoryFree} MB")
        #         output.append(f"GPU Memory Used: {gpu.memoryUsed} MB")
        #         output.append(f"GPU Load: {gpu.load * 100}%")
        #         output.append(f"GPU Temperature: {gpu.temperature}°C")
    
        return "\n".join(output)
Behavior3/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. It clearly describes the tool's read-only behavior and the types of information returned, but lacks details on performance, rate limits, or error handling. It adequately covers the core behavior without rich contextual disclosures.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured and front-loaded with the main purpose, followed by categorized details. It is appropriately sized for the tool's complexity, though some redundancy in listing information types could be slightly condensed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 provides complete context on what information is retrieved. It adequately compensates for the lack of structured fields, though it doesn't specify output format or potential errors.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose and output, not parameters, meeting the baseline for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Get') and resource ('current system information'), with detailed breakdowns of what information is included (System, Node name, CPU, Memory, Disk). It effectively distinguishes this tool's comprehensive scope from any hypothetical alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving system information, but provides no explicit guidance on when to use this tool versus alternatives (e.g., specific vs. partial system info tools). Since there are no sibling tools, this is adequate but lacks explicit 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/allenbijo/mcp-sysinfo'

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