cygnus-ssh-mcp

Official

Overview Schema Source Related Servers Discussions Admin

ssh_host_disconnect

Closes the current SSH connection when finished with operations or before switching to another host. Returns disconnection status.

Instructions

Disconnect the current SSH connection if one exists.

Use this when you want to explicitly close the current SSH connection before connecting to a different host or when you're done with SSH operations.

Returns: Dictionary with disconnection status

Long-running calls: if this takes longer than the server's wait cap (default 50s), it
returns {"status": "in_progress", "handle_id": ...} instead of the result - the work keeps
running. Get the result by polling ssh_cmd_check_status(handle_id=...), which returns this
tool's normal response once finished. Do not call it again meanwhile. Only one such
operation runs at a time; another one started meanwhile fails with a 'busy' error.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0May 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations present, the description carries the full burden and does so well: it discloses the long-running/wait-cap behavior, the in_progress + handle_id return shape, the polling tool ssh_cmd_check_status, the 'do not call again' rule, and the single-concurrency 'busy' failure mode. The only gap is the no-connection/no-op or error behavior, which 'if one exists' hints at but never states.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose, then usage, then return, then the async caveat in clearly labeled blocks. Every block earns its place, though the long-running boilerplate is somewhat template-heavy for a zero-argument disconnect call.

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

Completeness4/5

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

An output schema exists so the return values need not be spelled out, yet the description still notes the disconnection-status dictionary plus the async envelope. Usage, concurrency, and recovery path are all covered; only the no-op/error case when no connection exists is left implicit.

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 zero parameters (empty object schema, additionalProperties false), so there is nothing for the description to clarify. Baseline of 4 applies.

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?

Specific verb (Disconnect) plus resource (the current SSH connection) with the scope qualifier 'if one exists'. It is trivially distinguishable from sibling connectors such as ssh_conn_connect, ssh_conn_is_connected, and ssh_conn_status without opening any schema.

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?

Gives explicit when-to-use conditions: before connecting to a different host, or when finished with SSH operations. It does not name a when-not case or an alternative tool (e.g. that simply letting the session lapse is an option), so it falls short of a full 5.

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

Deploy Server