Skip to main content
Glama
ffpy

my-mcp-ssh

by ffpy
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

connect

Establish an SSH session to a remote server using password or private key authentication, and receive the connection status.

Instructions

Connect to SSH server

Args:
    host: SSH server hostname or IP address (optional)
    port: SSH server port (optional, default 22)
    username: SSH username (optional)
    password: SSH password for authentication (optional)
    key_path: SSH private key file path for authentication (optional)
    key_passphrase: SSH private key passphrase if needed (optional)

Returns:
    Connection status

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNo
portNo
key_pathNo
passwordNo
usernameNo
key_passphraseNo

Tool Definition Quality

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It lists authentication methods (password/key) and says it returns connection status, but does not explain session lifecycle, side effects, or failure modes.

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 organized into an Args list and a Returns line, making it easy to scan. It is appropriately sized for the number of parameters, though it could be tightened by removing the word 'optional' repetition.

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 six parameters and no output schema, the description covers the parameters and return status adequately. However, it lacks context on connection behavior (e.g., persistent sessions, timeouts, or how to use the returned status).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description fully compensates by listing all six parameters with clear explanations of each (host, port, username, password, key_path, key_passphrase). This provides essential meaning beyond the bare schema.

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?

The description clearly states 'Connect to SSH server', using a specific verb and resource. It naturally distinguishes itself from sibling tools like disconnect, execute, and list_sessions.

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 implies usage by listing connection parameters and return status, but it does not explicitly state when to use this tool over alternatives or mention preconditions like needing an existing session.

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/ffpy/my-mcp-ssh'

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