List configured remote servers for SSH connections with metadata, tags, and connection details. Filter by tag to find specific servers for secure management.
List all configured remote servers available for SSH connections with their metadata, tags, and connection details (excluding sensitive credentials).
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Optional tag to filter servers by (e.g. "production", "database", "web"). |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description is the only source of behavioral information. It clarifies that this is a read-only enumeration and explicitly excludes sensitive credentials, which is important safety-relevant behavior. It could mention authentication requirements or return format, but the stated exclusions add meaningful transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that leads with the primary action and result. It avoids unnecessary filler and places the most important information first.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple listing tool with one optional parameter, the description provides sufficient context: what is listed, what fields are available, and what is deliberately excluded. It could mention output format or pagination, but the absence is not critical for this straightforward read-only operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter, 'tag', is fully described in the schema itself, so the description adds no additional meaning beyond what the schema already provides. The baseline score applies because the schema covers the parameter adequately.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and clear resource ('configured remote servers'), and it distinguishes this tool from its siblings by focusing on discovery/inventory rather than execution or inspection. The inclusion of 'metadata, tags, and connection details' further clarifies the read-only purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear contextual purpose — listing configured SSH servers — but does not explicitly state when to prefer this tool over siblings like ssh_execute_command or ssh_test_connection. There is no when-to-use or when-not-to-use guidance, though the purpose is easy to infer.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.