Skip to main content
Glama
bvisible

MCP SSH Manager

ssh_session_close

Close SSH connections to remote servers by specifying a session ID or terminating all active sessions. This tool helps manage server resources and maintain security by ending unused connections.

Instructions

Close an SSH session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionYesSession ID to close (or "all" to close all sessions)

Implementation Reference

  • Registration of 'ssh_session_close' tool in the 'sessions' group of the centralized tool registry used for conditional tool enablement based on user configuration.
    sessions: [
      'ssh_session_start',
      'ssh_session_send',
      'ssh_session_list',
      'ssh_session_close'
    ],
  • Core helper function that closes an SSH session by ID by calling the session's close method and removing it from the active sessions map. This implements the primary logic for the ssh_session_close tool.
    /**
     * Close a session
     */
    export function closeSession(sessionId) {
      const session = sessions.get(sessionId);
    
      if (!session) {
        throw new Error(`Session ${sessionId} not found`);
      }
    
      session.close();
      return true;
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 states the action ('Close') but doesn't disclose behavioral traits such as whether this is destructive (likely yes, as it terminates sessions), permission requirements, error conditions (e.g., invalid session ID), or what happens on success/failure. This leaves critical operational details unspecified.

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. It's front-loaded with the core action and resource, making it highly efficient and easy to parse. Every word earns its place by conveying essential information without redundancy.

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 (a destructive operation with no annotations and no output schema), the description is incomplete. It doesn't explain what 'closing' entails (e.g., terminating connections, freeing resources), potential side effects, or expected outcomes. For a tool that likely alters system state, more context is needed to ensure safe and correct usage.

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%, with the parameter 'session' well-documented in the schema as accepting a Session ID or 'all'. The description adds no additional parameter semantics 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 ('Close') and resource ('SSH session'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'ssh_tunnel_close' or 'ssh_session_list', which would require mentioning it specifically terminates interactive sessions rather than tunnels or other session-related operations.

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 session from 'ssh_session_start'), exclusions, or relationships with siblings like 'ssh_session_list' for identifying sessions to close. Usage context is implied but not explicitly stated.

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

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