Skip to main content
Glama
batteryshark

System Information MCP Server

by batteryshark

get_full_system_report

Generate a complete system diagnostic report covering hardware, network, storage, devices, and user environment for comprehensive troubleshooting and system analysis.

Instructions

Get complete system analysis - runs all diagnostic tools.

Comprehensive system report including hardware, network, storage, devices, and user environment. Use for complete system analysis and thorough troubleshooting sessions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'get_full_system_report' tool. It is registered via the @mcp.tool decorator and orchestrates calls to various helper functions from collectors.py to generate a comprehensive system report as text content.
    @mcp.tool
    def get_full_system_report() -> ToolResult:
        """Get complete system analysis - runs all diagnostic tools.
        
        Comprehensive system report including hardware, network, storage, 
        devices, and user environment. Use for complete system analysis
        and thorough troubleshooting sessions.
        """
        info_sections = []
        info_sections.append("# Complete System Report")
        info_sections.append(f"*Generated: {datetime.now().strftime('%Y-%m-%d %H:%M:%S')}*\n")
        
        try:
            # Collect all information sections
            info_sections.extend(get_system_identity())
            info_sections.extend(get_hardware_info())
            info_sections.extend(get_display_info())
            info_sections.extend(get_network_info())
            info_sections.extend(get_storage_info())
            info_sections.extend(get_connectivity_devices())
            from .collectors import get_running_processes as get_processes_data
            info_sections.extend(get_processes_data())
            info_sections.extend(get_network_ports())
            info_sections.extend(get_user_session_info())
            info_sections.extend(get_time_locale_info())
            
        except Exception as e:
            info_sections.append(f"\n⚠️ **Error collecting system info**: {str(e)}")
        
        # Footer
        info_sections.append("\n---")
        info_sections.append("*Complete system analysis finished*")
        
        return text_response("\n".join(info_sections))
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 mentions the tool 'runs all diagnostic tools' and is 'comprehensive,' but lacks details on execution time, resource usage, permissions required, or output format. For a tool with no annotations that performs system analysis, this is a significant gap in transparency.

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 appropriately sized with two paragraphs: the first states the action and scope, the second elaborates on components and usage. Each sentence adds value, but the second paragraph could be slightly more front-loaded by integrating usage context earlier. Overall, it's efficient with minimal waste.

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 complexity of a comprehensive system analysis tool with no annotations and no output schema, the description is moderately complete. It covers purpose and usage but lacks behavioral details like execution behavior, output structure, or error handling. With siblings available for specific checks, it's adequate but has clear gaps for informed tool selection.

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, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter information, which is appropriate. Baseline is 4 for zero parameters, as it avoids unnecessary details.

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 with specific verbs ('Get complete system analysis', 'runs all diagnostic tools') and identifies the resource ('complete system report'). It distinguishes from siblings by mentioning it includes hardware, network, storage, devices, and user environment, which are covered by separate sibling tools. However, it doesn't explicitly name the sibling tools it aggregates, keeping it from a perfect score.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool ('for complete system analysis and thorough troubleshooting sessions'), which implies it's for comprehensive diagnostics rather than specific checks. It doesn't explicitly state when not to use it or name alternatives, but the context strongly suggests using sibling tools for focused queries instead.

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/batteryshark/mcp-sysinfo'

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