Skip to main content
Glama

ssh_get_status

Check SSH connection status to monitor active sessions and verify remote server connectivity in the mcpHydroSSH environment.

Instructions

Get SSH connection status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connectionIdNoConnection ID (optional, shows all connections if not provided)

Implementation Reference

  • Handler implementation for 'ssh_get_status'. It calls sshManager.getStatus or sshManager.getAllStatuses.
    case 'ssh_get_status': {
      const connectionId = args.connectionId as string | undefined;
      if (connectionId) {
        const status = sshManager.getStatus(connectionId);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(status, null, 2),
            },
          ],
        };
      } else {
        const statuses = sshManager.getAllStatuses();
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(statuses, null, 2),
            },
          ],
        };
      }
    }
  • Tool definition and input schema for 'ssh_get_status'.
      name: 'ssh_get_status',
      description: 'Get SSH connection status',
      inputSchema: {
        type: 'object',
        properties: {
          connectionId: {
            type: 'string',
            description: 'Connection ID (optional, shows all connections if not provided)',
          },
        },
        required: [],
      },
    },
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 but reveals almost nothing. It doesn't specify what status values are returned (boolean, string enum, object?), whether this performs an active health check or passive lookup, or that omitting connectionId returns all connections (a key behavioral trait only documented in the schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief at four words with no redundancy. However, it may be excessively concise—sacrificing necessary context for brevity. The single sentence is front-loaded but undersized for the tool's complexity.

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 absence of output schema and annotations, the description should explain what 'status' means and what data structure is returned. It also omits the important behavior that this can function as a list-all-connections tool when no ID is provided, leaving a significant gap for an AI agent determining how to monitor connection states.

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 that connectionId is optional and controls filtering vs. listing all connections. The description adds no semantic information beyond what the schema already provides, but meets the baseline expectation given the complete schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description provides a basic verb ('Get') and resource ('SSH connection status'), but 'status' remains ambiguous—it could mean connection health, configuration state, or active socket status. It fails to distinguish from ssh_list_servers (which lists configured servers) or clarify whether this checks established sessions vs. server configurations.

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 like ssh_connect (which might implicitly check status) or ssh_list_servers. It doesn't mention prerequisites (e.g., needing an existing connectionId from a previous connection) or when status checking is necessary before ssh_exec.

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/hydroCoderClaud/mcpHydroSSH'

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