Skip to main content
Glama
cygnussystems

cygnus-ssh-mcp

Official
by cygnussystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ssh_conn_host_info

Retrieve detailed SSH connection status and host system info, including hardware, memory, disk usage, and capability warnings.

Instructions

Get detailed SSH connection status and system information.

Returns: Dictionary containing full connection status and detailed system info including hardware, memory, disk usage, and more. For a 'linux' or 'flex' (non-Linux/macOS/Windows) connection, also includes 'capabilities' (probed GNU/BusyBox-coreutils feature support) and 'capability_warnings' (plain-English list of confirmed gaps) - see ssh_conn_connect's docstring for what these mean.

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
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it discloses async behavior (in_progress + handle_id after the 50s wait cap), the required polling tool, the prohibition on calling again during the wait, and the one-at-a-time concurrency limit with a 'busy' failure mode. It also describes the returned system details and capability fields for specific connection types.

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?

The description is front-loaded with the purpose and then uses clear sections ('Returns:' and 'Long-running calls:'). It is somewhat long, but the async and concurrency details earn their place because they change how an agent must invoke and follow up on the tool.

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?

Given that an output schema exists, the description does not need to explain return values, yet the extra return-value context is helpful. It covers the async and concurrency behavior completely, but it still lacks explicit sibling differentiation from ssh_conn_status or ssh_conn_is_connected.

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, so the baseline is 4. The empty schema and description correctly reflect that no input arguments are needed, and there are no parameter semantics to clarify.

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 states a specific verb and resource: 'Get detailed SSH connection status and system information.' It is clear what the tool retrieves, but it does not explicitly distinguish itself from sibling tools like ssh_conn_status or ssh_conn_is_connected, leaving mild ambiguity about which connection-status tool to choose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives useful usage guidance for long-running calls: poll ssh_cmd_check_status with the returned handle_id, do not call again meanwhile, and only one such operation runs at a time. However, it provides no when-to-use guidance relative to alternatives such as ssh_conn_status or ssh_conn_is_connected.

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

Deploy Server

Other Tools