ssh_disconnect
Disconnect from an Ubuntu server using its alias to terminate the SSH session.
Instructions
Disconnect from a server.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| alias | Yes |
Disconnect from an Ubuntu server using its alias to terminate the SSH session.
Disconnect from a server.
| Name | Required | Description | Default |
|---|---|---|---|
| alias | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description only states the action. Does not disclose side effects, error conditions, or whether it terminates all sessions for the alias.
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?
Extremely concise at three words, but no structure or additional context. While brevity is good, it sacrifices clarity and completeness.
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 tool with one parameter and no output schema, the description is insufficient. It fails to explain the parameter or the expected state of the system (e.g., must be connected).
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?
Schema description coverage is 0%. The description does not explain that 'alias' is the server identifier from ssh_connect. Agent cannot infer the parameter's meaning or expected format.
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?
Description clearly states the action 'disconnect' and resource 'server', using a specific verb. It distinguishes from sibling tool ssh_connect which does the opposite.
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?
No guidance on when to use this tool vs alternatives. No instructions about prerequisites like an active SSH session or that alias must refer to an existing connection.
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/smccauley-dev/ubuntu-ssh-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server