Skip to main content
Glama

ssh_close_session

Terminates SSH connections to remote servers by closing active sessions, helping manage resources and maintain security.

Instructions

Closes an SSH session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesSession ID to close

Implementation Reference

  • Implementation of the `closeSession` method that removes the session from the manager and closes the SSH and SFTP connections.
     * Closes an SSH session
     */
    async closeSession(sessionId: string): Promise<boolean> {
      logger.debug('Closing SSH session', { sessionId });
    
      const session = this.sessions.get(sessionId);
      if (!session) {
        logger.warn('Session not found for closing', { sessionId });
        return false;
      }
    
      try {
        await session.sftp.end();
        session.ssh.dispose();
      } catch (error) {
        logger.warn('Error closing session', { sessionId, error });
      }
    
      this.sessions.delete(sessionId);
      logger.info('SSH session closed', { sessionId });
      return true;
    }
  • src/mcp.ts:395-400 (registration)
    Tool handler registration and execution logic for `ssh_close_session` in `src/mcp.ts`.
    case 'ssh_close_session': {
      const { sessionId } = SessionIdSchema.parse(args);
      const result = await sessionManager.closeSession(sessionId);
      logger.info('SSH session closed', { sessionId });
      return { content: [{ type: 'text', text: JSON.stringify(result, null, 2) }] };
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like whether closing is destructive, if it requires specific permissions, error handling, or side effects (e.g., terminating processes). 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 zero waste. It's appropriately sized and front-loaded, 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 no annotations, no output schema, and a mutation tool, the description is incomplete. It lacks context on prerequisites, effects, error cases, or relationship to sibling tools, leaving significant gaps for an agent to use it correctly.

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 the 'sessionId' parameter. The description adds no meaning beyond what the schema provides, such as format examples or where to get the sessionId (e.g., from 'ssh_list_sessions'). Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('Closes') and resource ('an SSH session'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'ssh_list_sessions' or 'ssh_open_session' beyond the basic action, missing explicit scope or relationship context.

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 or prerequisites. It doesn't mention if it should be used after 'ssh_open_session' or in cleanup scenarios, 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/oaslananka/mcp-ssh-tool'

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