Skip to main content
Glama
simon-ami

Windows CLI MCP Server

get_current_directory

Retrieve the current working directory path in Windows CLI environments to verify file locations and navigate system directories.

Instructions

Get the current working directory

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for 'get_current_directory' tool that retrieves and returns the current working directory using Node.js process.cwd().
    case 'get_current_directory': {
      const currentDir = process.cwd();
      return { content: [{ type: 'text', text: `Current working directory: ${currentDir}` }] };
    }
  • src/index.ts:525-531 (registration)
    Registration of the 'get_current_directory' tool in the ListToolsRequestSchema handler, including its description and input schema (no parameters required).
      name: "get_current_directory",
      description: "Get the current working directory",
      inputSchema: {
        type: "object",
        properties: {} // No input parameters needed
      }
    }
  • Input schema definition for the 'get_current_directory' tool, specifying an empty object (no input parameters).
      inputSchema: {
        type: "object",
        properties: {} // No input parameters needed
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool does but doesn't disclose behavioral traits such as whether it's read-only (implied by 'Get'), what permissions are required, if it has side effects, or what format the output returns. This leaves significant gaps for an agent to understand the tool's behavior.

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, clear sentence with zero waste. It's front-loaded with the essential information and appropriately sized for a simple tool with no parameters, making it highly efficient.

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 the tool's simplicity (0 parameters, no annotations, no output schema), the description is minimally adequate. It states the purpose but lacks context about usage, behavioral details, or output format. For such a straightforward tool, this might suffice, but it doesn't provide complete guidance for an agent in the broader SSH/command execution context.

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 0 parameters, and the schema description coverage is 100% (though empty). The description doesn't need to add parameter details, so it appropriately avoids redundancy. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce confusion.

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 clearly states the action ('Get') and resource ('current working directory'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_command_history' or 'read_ssh_connections' which might also retrieve information, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention context like needing to know the directory for executing commands or navigating files, nor does it reference sibling tools that might serve related purposes in the SSH/command execution context.

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/simon-ami/win-cli-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server