Skip to main content
Glama
carlosedp

Windows MCP Server

by carlosedp

Windows-drives

Lists all drives detected by Windows, including local disks and removable devices.

Instructions

Get a list of all drives in the Windows system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:85-94 (handler)
    The tool 'Windows-drives' handler function 'get_drives' that returns a list of all drive letters by calling utils._enumerate_drives().
    @mcp.tool(
            name="Windows-drives",
            description="Get a list of all drives in the Windows system",
    )
    def get_drives() -> list[str]:
        """Get a list of all drives in the Windows system."""
        try:
            return utils._enumerate_drives()
        except Exception:
            return []
  • main.py:85-88 (registration)
    The @mcp.tool decorator that registers 'Windows-drives' with FastMCP.
    @mcp.tool(
            name="Windows-drives",
            description="Get a list of all drives in the Windows system",
    )
  • utils.py:1-8 (helper)
    The _enumerate_drives() helper function that uses ctypes and GetLogicalDrives Win32 API to enumerate available drive letters.
    # Helper utilities for robustness
    def _enumerate_drives() -> list[str]:
        """Return list of available drive letters, e.g., ['C', 'D']"""
        import ctypes
        import string
    
        bitmask = ctypes.windll.kernel32.GetLogicalDrives()
        return [letter for i, letter in enumerate(string.ascii_uppercase) if bitmask & (1 << i)]
Behavior3/5

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

With no annotations, the description carries the full burden for behavioral disclosure. It correctly indicates a read operation ('Get a list'), but does not add any extra context such as whether the list includes removable drives or requires admin privileges. The description is adequate but minimal.

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 is front-loaded and contains no redundant words. Every word serves a purpose.

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 that there are no parameters and an output schema is present, the description is largely complete. However, it could optionally mention the type of drives included (e.g., all physical and logical drives) to provide more context, so it falls just short of perfect.

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 is fully covered (100% description coverage). According to the calibration, zero parameters baseline is 4. The description does not add parameter info because none exist, which is appropriate.

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 verb 'Get' and resource 'list of all drives in the Windows system'. It accurately identifies the tool's purpose and distinguishes it from sibling tools like Windows-drives-status-simple and Windows-drive-status, which focus on status rather than listing.

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 is provided on when to use this tool versus alternatives. The presence of similar sibling tools (Windows-drive-status, Windows-drives-status-simple) suggests that usage context matters, but the description does not indicate when to choose this tool over them.

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