Skip to main content
Glama
carlosedp

Windows MCP Server

by carlosedp

Windows-network-info

Retrieve Windows network information including IP addresses, connection status, and adapter details.

Instructions

Get network information of the Windows system.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • main.py:154-157 (registration)
    Registration of the Windows-network-info tool using the @mcp.tool decorator, assigning its name and description.
    @mcp.tool(
            name="Windows-network-info",
            description="Get network information of the Windows system."
    )
  • main.py:158-169 (handler)
    Handler function that collects network interface IPv4 addresses using psutil.net_if_addrs() and filters by socket.AF_INET family.
    def get_network_info() -> dict[str, str]:
        """Get network information of the Windows system."""
        import psutil
        import socket
    
        net_info = psutil.net_if_addrs()
        result = {}
        for interface, addresses in net_info.items():
            for address in addresses:
                if address.family == socket.AF_INET:
                    result[interface] = address.address
        return result if result else {"error": "No network interfaces found."}
Behavior2/5

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

With no annotations, the description carries full burden but only states purpose. It does not disclose behavioral traits like read-only nature, authorization needs, or output structure, though output schema exists.

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

Conciseness4/5

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

Single sentence, front-loaded, and to the point. Could be slightly expanded but remains concise.

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 zero parameters and an output schema, the description is complete enough to understand the tool's purpose. It does not need to explain return values.

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, so baseline is 4. Description adds no parameter-specific details but none needed.

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?

Description clearly states the verb 'Get' and the resource 'network information', and the scope 'Windows system'. It effectively distinguishes from sibling tools that cover CPU, drives, memory, etc.

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?

No guidance on when to use this tool vs alternatives. Does not mention exclusions or context for selection among similar system info tools.

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