Skip to main content
Glama

ssh_disconnect

Terminate an active SSH connection to a remote server. Use this tool to close sessions and free up resources when remote operations are complete.

Instructions

Disconnect from an SSH server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdYesConnection ID to disconnect

Implementation Reference

  • Executes the ssh_disconnect tool: validates input with DisconnectSSHSchema, retrieves SSH connection by ID from pool, disposes the connection, removes from pool and context maps, returns 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 input schema for ssh_disconnect tool requiring 'connectionId' string parameter.
    const DisconnectSSHSchema = z.object({
      connectionId: z.string().describe('Connection ID to disconnect')
    });
  • src/index.ts:256-265 (registration)
    Tool registration in ListToolsRequestSchema handler: defines name, description, and inputSchema matching the DisconnectSSHSchema.
      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:487-488 (registration)
    Dispatch/registration in CallToolRequestSchema switch statement: maps tool name to handler function.
    case 'ssh_disconnect':
      return await this.handleSSHDisconnect(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Disconnect') but doesn't explain what happens upon disconnection (e.g., if it terminates sessions, releases resources, or has side effects), nor does it mention permissions, rate limits, or error conditions. This is a significant gap 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 any wasted words. It is appropriately sized and front-loaded, making it easy for an agent 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 complexity of disconnecting from an SSH server (a mutation operation), the lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like effects, errors, or return values, leaving the agent with insufficient context to use the tool safely and effectively.

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, with the parameter 'connectionId' clearly documented. The description doesn't add any meaning beyond what the schema provides, such as explaining what a connection ID is or how to obtain it. Given the high schema coverage, the baseline score of 3 is appropriate.

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'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from sibling tools like 'ssh_close_interactive_shell', which might also involve disconnection, 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, such as 'ssh_close_interactive_shell' or other SSH-related tools. It lacks context about prerequisites (e.g., needing an active connection) or exclusions, leaving the agent to infer usage from the name alone.

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

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