Skip to main content
Glama
PWalaGov

Enhanced Directory Context MCP Server

by PWalaGov

set_working_directory

Specify a directory path to establish the active working location for context extraction and analysis operations.

Instructions

Set the working directory for context extraction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directoryYesPath to the directory to analyze

Implementation Reference

  • The handler function for 'set_working_directory' that validates the directory path, updates the server's working directory, and returns a confirmation message.
    async setWorkingDirectory(directory) {
      try {
        const resolvedPath = path.resolve(directory);
        const stats = await fs.stat(resolvedPath);
        
        if (!stats.isDirectory()) {
          throw new Error('Path is not a directory');
        }
        
        this.workingDirectory = resolvedPath;
        
        return {
          content: [
            {
              type: 'text',
              text: `Working directory set to: ${this.workingDirectory}`,
            },
          ],
        };
      } catch (error) {
        throw new McpError(ErrorCode.InvalidParams, `Invalid directory: ${error.message}`);
      }
    }
  • Input schema definition for the 'set_working_directory' tool, specifying a required 'directory' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        directory: {
          type: 'string',
          description: 'Path to the directory to analyze',
        },
      },
      required: ['directory'],
    },
  • server.js:52-64 (registration)
    Tool registration entry in the listTools response, including name, description, and input schema.
      name: 'set_working_directory',
      description: 'Set the working directory for context extraction',
      inputSchema: {
        type: 'object',
        properties: {
          directory: {
            type: 'string',
            description: 'Path to the directory to analyze',
          },
        },
        required: ['directory'],
      },
    },
  • Dispatch case in the main CallToolRequestSchema handler that invokes the setWorkingDirectory method.
    case 'set_working_directory':
      return await this.setWorkingDirectory(args.directory);
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 mentions 'Set' and 'context extraction' but doesn't disclose behavioral traits such as whether this affects subsequent operations, requires specific permissions, or has side effects. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with no wasted words. It's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity as a mutation operation with no annotations and no output schema, the description is insufficient. It lacks details on behavior, effects, or integration with sibling tools, making it incomplete for effective agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents the 'directory' parameter. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, resulting in a baseline score.

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 ('Set') and the target ('working directory for context extraction'), making the purpose understandable. However, it doesn't distinguish this tool from potential alternatives like 'create_directory' or specify what 'context extraction' entails, preventing a perfect 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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'create_directory', 'get_directory_structure', and 'analyze_project_context', the description lacks context about prerequisites, timing, or comparisons, leaving usage ambiguous.

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/PWalaGov/File-Control-MCP'

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