Skip to main content
Glama
carlosedp

Windows MCP Server

by carlosedp

Windows-cpu-info

Retrieves Windows CPU information including utilization, model, and core count to monitor system performance.

Instructions

Get CPU information of the Windows system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:171-173 (registration)
    Registration of the 'Windows-cpu-info' tool via the @mcp.tool decorator with its name and description.
    @mcp.tool(
            name="Windows-cpu-info",
            description="Get CPU information of the Windows system."
  • main.py:175-187 (handler)
    Handler function 'get_cpu_info' that executes the tool logic: retrieves CPU model, core count, and frequency using psutil and platform modules.
    def get_cpu_info() -> str:
        """Get CPU information of the Windows system."""
        import psutil
        import platform
    
        cpu_count = psutil.cpu_count(logical=True)
        cpu_freq = psutil.cpu_freq()
        cpu_model = platform.processor()
        if cpu_freq is not None:
            current, min_f, max_f = cpu_freq.current, cpu_freq.min, cpu_freq.max
        else:
            current, min_f, max_f = 0.0, 0.0, 0.0
        return f"Model: {cpu_model}, CPU Count: {cpu_count}, Frequency: {current} MHz, Min: {min_f} MHz, Max: {max_f} MHz"
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states what the tool does without mentioning any side effects, permissions, performance implications, or whether the data is static or real-time. This is insufficient for a tool with no annotation support.

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

Conciseness3/5

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

The description is a single short sentence, making it concise but lacking structure or front-loading of key details. It does not waste words, but could benefit from adding brief usage context or output hints without increasing length significantly.

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 no parameters and an existing output schema, the description is minimally complete for a simple read operation. However, it does not hint at the output format or provide context about what kind of CPU information is returned, which could help an agent decide if the tool meets its need.

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 no parameters, and the input schema coverage is 100%. The description adds no parameter information, which is acceptable per guidelines (baseline 4 for 0 params). No additional meaning is needed beyond what the schema provides.

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 'Get CPU information of the Windows system' clearly states the tool returns CPU-related data, distinguishing it from siblings like Windows-memory-info or Windows-gpu-info. However, it does not specify what aspects of CPU info (e.g., utilization, model, cores), leaving some ambiguity.

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 provides no explicit guidance on when to use this tool versus alternatives. It is implied by the tool name and sibling context (e.g., use for CPU info, not memory or drives), but no exclusions or recommendations are given.

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