Skip to main content
Glama

ssh_connect_raw

Directly connect to target assets via a bastion host by specifying connection parameters such as host, user, and password, enabling temporary SSH sessions without relying on config.json.

Instructions

直接指定参数连接(不依赖 config.json),用于临时连接。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNo堡垒机地址service.rrzuji.net
nameNo会话名称(可选)
portNo堡垒机端口
userNo堡垒机用户名xiaolinxin
proxyNoSOCKS5 代理地址
searchNo搜索字符串,如 /39.108.73.45/39.108.73.45
timeoutNo连接超时秒数
key_pathNoSSH 私钥路径(auth_type=key 时使用)
passwordNo堡垒机密码
auth_typeNo认证方式 (password/key)password
server_idNo目标资产 ID1
target_dirNo登录后工作目录

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only repeats the tool's basic function ('connect directly with parameters') and fails to disclose behavioral traits such as authentication requirements, side effects, or error handling.

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 a single, concise sentence that conveys the core differentiator. While brief, it is efficient with no wasted words, though it could be slightly more structured.

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?

With 12 parameters and an output schema (not shown), the description is too minimal. It omits details about return values, connection behavior, and error conditions, leaving the agent with incomplete context for a complex tool.

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

Parameters3/5

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

All 12 parameters are documented in the input schema with descriptions and defaults, so schema coverage is 100%. The description adds no additional parameter context beyond what the schema already provides, which is adequate.

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 clearly states the tool connects directly with parameters without relying on config.json, and is for temporary connections. This differentiates it from sibling tools like ssh_connect, giving a specific verb and resource.

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 context (temporary connections, direct parameters) but does not explicitly state when to avoid this tool or mention alternatives like ssh_connect for config-based connections.

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/xiao-linxin/mcp-ssh'

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