Skip to main content
Glama
carlosedp

Windows MCP Server

by carlosedp

Windows-memory-info

Retrieve real-time Windows memory usage data including total, used, and available memory. Monitor system performance.

Instructions

Get memory information of the Windows system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:136-139 (registration)
    Registration of the 'Windows-memory-info' MCP tool via @mcp.tool decorator with name and description.
    @mcp.tool(
            name="Windows-memory-info",
            description="Get memory information of the Windows system."
    )
  • main.py:140-152 (handler)
    The handler function 'get_memory_info' that uses psutil.virtual_memory() to retrieve and return total, available, and used memory in GB.
    def get_memory_info() -> dict[str, str]:
        """Get memory information of the Windows system."""
        import psutil
    
        memory = psutil.virtual_memory()
        total_memory = memory.total / (1024 ** 3)
        available_memory = memory.available / (1024 ** 3)
        used_memory = memory.used / (1024 ** 3)
        return {
            "total_memory": f"{total_memory:.2f} GB",
            "available_memory": f"{available_memory:.2f} GB",
            "used_memory": f"{used_memory:.2f} GB"
        }
Behavior2/5

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

No annotations are provided, and the description lacks any behavioral details such as what the output contains, permissions needed, or side effects. The description does not compensate for missing annotations.

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 sentence that efficiently conveys the purpose with no wasted words. It is front-loaded and appropriate for a simple getter tool.

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?

While the tool has no parameters and an output schema exists, the description does not explain what memory information is returned (e.g., total, used, free). For a simple tool this is adequate but could be improved.

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?

There are no parameters, so the schema coverage is complete. With zero parameters, the baseline score is 4, and the description does not detract from that.

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 uses a specific verb 'Get' and clearly identifies the resource as 'memory information of the Windows system'. This distinguishes it from sibling tools like Windows-cpu-info or Windows-drives.

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?

No explicit guidance on when to use this tool versus alternatives is provided. However, the tool's purpose is clear and siblings cover different resources, so usage context is implied.

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