Skip to main content
Glama
nwnusun-cool

MCP SSH Tools Server

by nwnusun-cool

list_servers

List all configured SSH servers for remote management. View available connections to execute commands, transfer files, or manage systems through the MCP SSH Tools Server.

Instructions

列出所有配置的服务器

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • main.py:464-489 (handler)
    The handler function for the list_servers tool. It iterates over configured servers, checks connection status using mcp_manager, and returns a list of servers with details including name, IP, user, port, and connected status.
    @mcp.tool()
    def list_servers() -> Dict[str, Any]:
        """列出所有配置的服务器"""
        servers = []
        for name, config in mcp_manager.server_configs.items():
            # 检查连接状态
            is_connected = False
            if name in mcp_manager.active_connections:
                try:
                    transport = mcp_manager.active_connections[name].get_transport()
                    is_connected = transport and transport.is_active()
                except:
                    is_connected = False
            
            servers.append({
                "name": name,
                "ip": config.ssh_ip,
                "user": config.ssh_user,
                "port": config.ssh_port,
                "connected": is_connected
            })
        
        return {
            "servers": servers,
            "total_servers": len(servers)
        }
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 for behavioral disclosure. The description only states what the tool does ('list all configured servers') but provides no information about permissions needed, rate limits, whether the listing is paginated, what format the output takes, or any other behavioral characteristics. This leaves significant gaps for an agent trying to use this tool effectively.

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, efficient sentence in Chinese that directly states the tool's purpose with zero wasted words. It's appropriately front-loaded with the core functionality and doesn't include any unnecessary elaboration.

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?

Given that this is a simple listing tool with 0 parameters and an output schema exists (which should document return values), the description is minimally adequate. However, with no annotations and no behavioral context in the description, there are significant gaps in understanding how this tool behaves in practice. The existence of an output schema helps, but doesn't compensate for the lack of operational guidance.

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 has 0 parameters, and schema description coverage is 100% (though with no parameters, this is trivially true). The description doesn't need to explain any parameters, and with no parameters to document, it appropriately focuses on the tool's purpose. A baseline of 4 is appropriate for zero-parameter tools.

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 '列出所有配置的服务器' (List all configured servers) clearly states the verb ('list') and resource ('configured servers'), making the purpose immediately understandable. It doesn't specifically differentiate from siblings like 'list_directory' or 'test_connection', but the resource focus is clear enough for basic understanding.

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. With siblings like 'list_directory' (which might list files rather than servers) and 'add_server_config' (which modifies servers), there's no indication of when this listing operation is appropriate versus those other tools.

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/nwnusun-cool/mcp-server-ssh-tools'

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