Skip to main content
Glama
remote-ssh-mcp
by RuiFG

ssh_list_hosts

Read-only

List configured SSH hosts with stable IDs, connection status, and session working directories so you can choose the explicit hostId required by other SSH tools; credentials are never returned.

Instructions

List configured SSH hosts with stable IDs, connection status and this session's per-host working directories. Never returns credentials. All other SSH tools require an explicit hostId; there is no default host.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ssh_list_hosts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. Beyond that, the description adds genuinely useful behavior: it discloses the returned fields, guarantees credentials are never included, and clarifies that working directories are scoped to "this session" — which explains why idempotentHint is false despite this being a read.

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?

Three short sentences, front-loaded with the purpose and its return contents, followed by a security note and a routing constraint. Every sentence carries distinct information and nothing is repeated from the schema or annotations.

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

Completeness5/5

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

With no output schema, the description carries the burden of describing return values, and it does so precisely (stable IDs, connection status, per-host working directories). Being parameterless and annotated as a safe read, there is nothing further an agent needs before invoking it.

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 tool takes no parameters and the schema is an empty closed object, so there is nothing for the description to disambiguate. The baseline for a zero-parameter tool applies, and the description correctly spends no words on inputs.

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

Purpose5/5

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

States a specific verb and resource ("List configured SSH hosts") and immediately enumerates what each entry carries: stable IDs, connection status, and session working directories. It also distinguishes itself from the rest of the SSH family by noting that every other tool requires an explicit hostId, so an agent can place it in the catalog without opening sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The line "All other SSH tools require an explicit hostId; there is no default host" effectively tells the agent this is the discovery step before any host-scoped call. It stops short of an explicit imperative ("call this first to obtain a hostId") and names no exclusions, so it is clear context rather than complete routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.