Skip to main content
Glama
carlosedp

Windows MCP Server

by carlosedp

Windows-uptime

Get the current uptime of the Windows system to track duration since last boot.

Instructions

Get the uptime of the Windows system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:70-73 (registration)
    Registration of the 'Windows-uptime' tool via @mcp.tool decorator with name and description attributes.
    @mcp.tool(
            name="Windows-uptime",
            description="Get the uptime of the Windows system",
    )
  • main.py:74-83 (handler)
    Handler function 'get_windows_uptime' that calculates system uptime using psutil.boot_time() and time.time().
    def get_windows_uptime() -> str:
        """Get the uptime of the Windows system."""
        import psutil
        import time
    
        try:
            uptime_seconds = time.time() - psutil.boot_time()
            return f"Uptime: {uptime_seconds:.0f} seconds"
        except Exception as e:
            return f"Error retrieving uptime: {e}"
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description 'Get the uptime' implies a read-only, non-destructive operation. However, it does not explicitly state safety or permission requirements, which is a minor gap.

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?

Single sentence, highly concise with no unnecessary words. Front-loaded with the essential action.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with an output schema, the description is sufficient. It fully conveys the tool's purpose and behavior.

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?

No parameters exist, so schema coverage is 100%. The description does not need to add parameter details, achieving 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 tool retrieves system uptime. It distinguishes from sibling tools like Windows-system-info or Windows-last-boot-time by being specific to uptime.

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 purpose is self-explanatory; it's clear when to use this tool (to get uptime). No explicit exclusions or alternatives are needed given the simple query nature.

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/carlosedp/windows-mcp-server'

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