Skip to main content
Glama
widjis
by widjis

ssh_set_working_directory

Change the current working directory for an SSH connection to navigate remote file systems and execute commands from a specific location.

Instructions

Set the current working directory for a connection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdYesSSH connection ID
workingDirectoryYesWorking directory path to set as current

Implementation Reference

  • The handler function for 'ssh_set_working_directory' tool. Parses input, retrieves connection context, verifies the directory exists on the remote server using 'test -d', updates the connection's currentWorkingDirectory, and returns success message.
    private async handleSetWorkingDirectory(args: unknown) {
      const params = SetWorkingDirectorySchema.parse(args);
      
      const context = connectionContexts.get(params.connectionId);
      if (!context) {
        throw new McpError(
          ErrorCode.InvalidParams,
          `Connection ID '${params.connectionId}' not found`
        );
      }
    
      try {
        // Verify the directory exists
        const result = await context.ssh.execCommand(`test -d "${params.workingDirectory}" && echo "exists"`);
        if (result.code !== 0) {
          throw new McpError(
            ErrorCode.InvalidParams,
            `Directory '${params.workingDirectory}' does not exist or is not accessible`
          );
        }
    
        // Set the working directory
        context.currentWorkingDirectory = params.workingDirectory;
        
        return {
          content: [
            {
              type: 'text',
              text: `Working directory set to: ${params.workingDirectory}`,
            },
          ],
        };
      } catch (error) {
        if (error instanceof McpError) {
          throw error;
        }
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to set working directory: ${error instanceof Error ? error.message : String(error)}`
        );
      }
    }
  • Zod schema defining the input parameters for the ssh_set_working_directory tool: connectionId (string) and workingDirectory (string).
    const SetWorkingDirectorySchema = z.object({
      connectionId: z.string().describe('SSH connection ID'),
      workingDirectory: z.string().describe('Working directory path to set as current')
    });
  • src/index.ts:421-431 (registration)
    Registration of the 'ssh_set_working_directory' tool in the ListTools response, including name, description, and input schema matching the Zod schema.
      name: 'ssh_set_working_directory',
      description: 'Set the current working directory for a connection',
      inputSchema: {
        type: 'object',
        properties: {
          connectionId: { type: 'string', description: 'SSH connection ID' },
          workingDirectory: { type: 'string', description: 'Working directory path to set as current' }
        },
        required: ['connectionId', 'workingDirectory']
      },
    },
  • src/index.ts:513-514 (registration)
    Dispatch case in the CallToolRequest handler that routes to the handleSetWorkingDirectory method.
    case 'ssh_set_working_directory':
      return await this.handleSetWorkingDirectory(args);
  • Interface for connection context that stores the currentWorkingDirectory used by the set working directory handler.
    interface ConnectionContext {
      ssh: NodeSSH;
      currentWorkingDirectory?: string;
      defaultWorkingDirectory?: string;
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Set') but lacks details on permissions required, whether changes are persistent across sessions, error handling, or 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 that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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 involves mutation (setting a directory) with no annotations and no output schema, the description is incomplete. It doesn't explain what happens on success/failure, return values, or behavioral nuances, which are critical for an agent to use it correctly in context with siblings.

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 schema already documents both parameters ('connectionId' and 'workingDirectory') fully. The description implies setting a directory path but adds no syntax, format, or validation details beyond what the schema provides, meeting the baseline for high coverage.

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 resource ('current working directory for a connection'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'ssh_get_working_directory' or 'ssh_execute' which might also involve directory operations, missing full sibling distinction.

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 prerequisites (e.g., needing an active SSH connection), exclusions, or compare to siblings like 'ssh_get_working_directory' for retrieval or 'ssh_execute' for commands in a directory, leaving usage context unclear.

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/widjis/mcp-ssh'

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