Skip to main content
Glama
widjis
by widjis

ssh_disconnect

Terminate an active SSH connection to free up resources and manage server sessions. Specify the connection ID to close the established remote session.

Instructions

Disconnect from an SSH server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdYesConnection ID to disconnect

Implementation Reference

  • The handler function that executes the ssh_disconnect tool. It validates input with DisconnectSSHSchema, retrieves the NodeSSH instance from connectionPool, calls dispose() to disconnect, removes entries from connectionPool and connectionContexts, and returns a success message.
    private async handleSSHDisconnect(args: unknown) {
      const params = DisconnectSSHSchema.parse(args);
      
      const ssh = connectionPool.get(params.connectionId);
      if (!ssh) {
        throw new McpError(
          ErrorCode.InvalidParams,
          `Connection ID '${params.connectionId}' not found`
        );
      }
    
      ssh.dispose();
      connectionPool.delete(params.connectionId);
      
      // Clean up connection context
      connectionContexts.delete(params.connectionId);
    
      return {
        content: [
          {
            type: 'text',
            text: `Disconnected from ${params.connectionId}`,
          },
        ],
      };
    }
  • Zod schema defining the input parameters for the ssh_disconnect tool: requires a connectionId string.
    const DisconnectSSHSchema = z.object({
      connectionId: z.string().describe('Connection ID to disconnect')
    });
  • src/index.ts:256-264 (registration)
    Registration of the ssh_disconnect tool in the listTools response, specifying name, description, and inputSchema matching the handler schema.
    name: 'ssh_disconnect',
    description: 'Disconnect from an SSH server',
    inputSchema: {
      type: 'object',
      properties: {
        connectionId: { type: 'string', description: 'Connection ID to disconnect' }
      },
      required: ['connectionId']
    },
  • src/index.ts:488-489 (registration)
    Switch case in CallToolRequestSchema handler that routes ssh_disconnect calls to the handleSSHDisconnect method.
      return await this.handleSSHDisconnect(args);
    case 'ssh_execute':
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 but lacks details on effects (e.g., whether it terminates all sessions, requires specific permissions, or handles errors). This is a significant gap for a tool that likely involves network operations.

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, direct sentence with zero wasted words, making it highly efficient and front-loaded. It immediately conveys the core 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 complexity of SSH operations and lack of annotations or output schema, the description is insufficient. It doesn't cover behavioral aspects like side effects, error handling, or return values, leaving gaps for safe and effective tool invocation.

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?

The input schema has 100% description coverage, documenting the 'connectionId' parameter clearly. The description adds no additional meaning beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 ('Disconnect') and target resource ('from an SSH server'), making the purpose immediately understandable. It doesn't differentiate from sibling tools like 'ssh_close_interactive_shell', which might handle a specific type of disconnection, so it misses the top 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 such as 'ssh_close_interactive_shell' or in what context disconnection is appropriate. The description assumes usage without specifying prerequisites or exclusions.

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