Skip to main content
Glama

ssh_list_servers

List all configured SSH servers in the mcpHydroSSH environment to view available remote connections for management.

Instructions

List all configured SSH servers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the `ssh_list_servers` tool, which maps configured servers to a simplified list and returns them as a JSON string.
    case 'ssh_list_servers': {
      const servers: ServerListItem[] = config.servers.map(s => ({
        id: s.id,
        name: s.name,
        host: s.host,
        port: s.port,
      }));
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(servers, null, 2),
          },
        ],
      };
    }
  • src/index.ts:44-52 (registration)
    The definition and registration of the `ssh_list_servers` tool, including its description and empty input schema.
    {
      name: 'ssh_list_servers',
      description: 'List all configured SSH servers',
      inputSchema: {
        type: 'object',
        properties: {},
        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. While 'List' implies a read-only operation, the description fails to specify what 'configured' entails (persistent storage vs. active connections), return format, or whether the operation is idempotent.

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 single sentence 'List all configured SSH servers' is optimally concise with no redundant words. The key verb and resource appear immediately at the front.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool without annotations or output schema, the description meets minimum viability by stating the core operation. However, it lacks context about what properties are returned for each server or what constitutes a 'configured' server in this system.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema contains zero parameters, establishing a baseline score of 4 per the evaluation rules. The description appropriately requires no additional parameter clarification.

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 uses the specific verb 'List' with the clear resource 'configured SSH servers', distinguishing it from connection-oriented siblings like ssh_connect and ssh_exec. However, it doesn't clarify the distinction from ssh_view_config, which might also access server information.

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 explicit guidance on when to use this tool versus alternatives like ssh_view_config or ssh_get_status. There are no 'when-not-to-use' caveats or prerequisites mentioned.

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