Skip to main content
Glama
carlosedp

Windows MCP Server

by carlosedp

Windows-system-info

Retrieve Windows system details including OS version, release, architecture, and hostname for real-time monitoring and diagnostics.

Instructions

Get Windows system information including OS version, release, architecture, and hostname

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:26-48 (handler)
    The tool registration (via @mcp.tool decorator) and handler function 'get_windows_name_version' that implements the 'Windows-system-info' tool logic. It uses platform and socket modules to retrieve OS version, release, architecture, and hostname, returning a dict of string key-value pairs.
    @mcp.tool(
            name="Windows-system-info",
            description="Get Windows system information including OS version, release, architecture, and hostname",
    )
    def get_windows_name_version() -> dict[str, str]:
        """Get Windows system information including OS version, release, architecture, and hostname."""
        import platform
        import socket
    
        name = platform.node()
        version = platform.version()
        release = platform.release()
        system = platform.system()
        architecture = platform.architecture()[0]
        hostname = socket.gethostname()
        return {
            "name": name,
            "system": system,
            "release": release,
            "version": version,
            "architecture": architecture,
            "hostname": hostname
        }
  • main.py:26-30 (registration)
    The @mcp.tool decorator registers the tool with name 'Windows-system-info' and provides its description.
    @mcp.tool(
            name="Windows-system-info",
            description="Get Windows system information including OS version, release, architecture, and hostname",
    )
    def get_windows_name_version() -> dict[str, str]:
  • main.py:13-16 (schema)
    The DriveInfo schema defined in the same file is not directly used by this tool (which returns a plain dict), but is included for context of the file's schema definitions.
    class DriveInfo(BaseModel):
        """Model for drive information."""
        name: str = Field(description="Drive name")
        used_spaceGB: float = Field(description="Used space in GB")
Behavior4/5

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

No annotations provided, so description carries full burden. It accurately describes a read-only information retrieval with no side effects. While the behavior is obvious, the description could additionally clarify that no modifications occur.

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, front-loaded with verb and resource, no unnecessary words. Efficient and clear.

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?

With no parameters, a clear list of output fields, and an output schema present, the description fully conveys what the tool does. No missing information.

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 in input schema, so baseline is 4. Description doesn't need to add parameter meaning.

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 purpose: getting Windows system information, listing specific fields (OS version, release, architecture, hostname). This differentiates it from sibling tools like Windows-cpu-info or Windows-drives that target specific components.

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 implies usage when general system info is needed, but provides no explicit guidance on when to use or not use this tool versus alternatives. No exclusions or context about sibling differentiation.

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