ssh_list_connections
Provides a list of all SSH connections, enabling you to view and manage active sessions.
Instructions
列出所有SSH连接
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Provides a list of all SSH connections, enabling you to view and manage active sessions.
列出所有SSH连接
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits like idempotency or side effects. Although listing is likely read-only, this is not explicitly stated.
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, front-loaded sentence with no wasted words. It efficiently conveys the tool's purpose.
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?
The description fails to specify what information the list contains (e.g., host, port, status) or the return format. Given the lack of output schema, the agent needs more detail to interpret the tool's output.
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 input schema has zero parameters, so no additional meaning is needed. Baseline for no parameters is 4.
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 '列出所有SSH连接' clearly states the action (list) and resource (SSH connections). It distinguishes from sibling tools like ssh_connect or ssh_disconnect, but lacks any qualifiers about scope or filtering.
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?
There is no guidance on when to use this tool versus alternatives such as ssh_list_config or ssh_list_async_commands. The description does not mention when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhijun/ssh-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server