Skip to main content
Glama
dknell

System Information MCP Server

by dknell

get_system_uptime_tool

Retrieve system uptime and boot information to monitor server availability and track system restart history.

Instructions

Retrieve system uptime and boot information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the 'get_system_uptime_tool' tool, registered via @app.tool() decorator. It delegates the core logic to the get_system_uptime helper function.
    @app.tool()
    def get_system_uptime_tool() -> Dict[str, Any]:
        """Retrieve system uptime and boot information."""
        return get_system_uptime()
  • Core helper function implementing the system uptime logic using psutil.boot_time(). Computes uptime in seconds, formats it, and returns boot time in ISO format.
    @cache_result("system_uptime", ttl=30)
    def get_system_uptime() -> Dict[str, Any]:
        """Retrieve system uptime and boot information."""
        try:
            boot_time = psutil.boot_time()
            current_time = time.time()
            uptime_seconds = int(current_time - boot_time)
    
            return {
                "boot_time": timestamp_to_iso(boot_time),
                "uptime_seconds": uptime_seconds,
                "uptime_formatted": format_uptime(uptime_seconds),
            }
    
        except Exception as e:
            logger.error(f"Error getting system uptime: {e}")
            raise
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 states the tool retrieves information, implying a read-only operation, but doesn't clarify aspects like permissions required, data format, or potential errors. For a tool with zero annotation coverage, 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.

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 annotations, but with an output schema), the description is reasonably complete. It specifies what information is retrieved, and the presence of an output schema means the description doesn't need to explain return values. However, it lacks context on usage compared to siblings, which is a minor gap.

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 the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics, so it meets the baseline expectation. No additional value is required or provided beyond the schema.

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 a specific verb ('retrieve') and resource ('system uptime and boot information'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'get_cpu_info_tool' or 'get_memory_info_tool', which also retrieve system information but for different resources.

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. It doesn't mention sibling tools or contexts where uptime information is needed over other system metrics, leaving the agent to infer usage based on the tool name alone.

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/dknell/mcp-system-info'

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