Skip to main content
Glama
jiahuidegit

SSH MCP Server

by jiahuidegit

exec_shell

Execute commands through an interactive shell for bastion host access. Specify target server by alias or host, or omit when only one connection is active.

Instructions

通过交互式 shell 模式执行命令(用于堡垒机穿透等不支持 exec 的场景)。必须指定目标服务器:使用 alias(推荐)或 host。只有一个活跃连接时可省略目标。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYes要执行的命令
aliasNo服务器别名(推荐)
hostNo服务器地址(多个活跃连接时必须指定 alias 或 host,单连接时可省略)
portNoSSH 端口(可选)
usernameNo用户名(可选,配合 host 使用)
timeoutNo命令超时时间(毫秒,最小 1000)
promptPatternNo自定义 shell 提示符正则表达式(可选,用于识别命令执行完成)
confirmationTokenNo危险命令确认 token
targetConfirmationTokenNo服务器切换确认 token
Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It mentions interactive shell mode and connection context, but fails to explain critical aspects like the purpose of confirmation tokens, potential destructive actions, error handling, or output behavior. The description is insufficient for safe tool invocation.

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

Conciseness5/5

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

The description is extremely concise (three short sentences) and front-loaded: first sentence states purpose, second gives key instruction, third covers edge case. No wasted words.

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

Completeness2/5

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

Despite a clear purpose, the description omits crucial context for a complex tool with 9 parameters, no output schema, and no annotations. It does not explain the interactive shell behavior, use for confirmation tokens, timeout behavior, or error handling. This leaves the agent underinformed.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining the relationship between alias/host and the single-connection rule, and recommends alias over host. This context goes beyond the schema descriptions.

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 it is for interactive shell mode in scenarios where exec is not supported (e.g., bastion host traversal), distinguishing it from sibling tools like exec, exec_batch, and exec_sudo.

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?

The description specifies when to use (scenarios where exec is not supported) and provides clear guidance on target server specification (alias recommended, host alternative, and omission allowed when only one active connection). However, it does not explicitly state when not to use or compare to other execution tools.

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/jiahuidegit/ssh-mcp-server'

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