Skip to main content
Glama

push_ssh

Establishes a named SSH layer that becomes the default for later tools, reusing existing connections to the same target and validating hosts; jump hosts pass through without consuming a layer.

Instructions

建立命名 ssh 层(成为默认层——后续工具缺省落它)。同落点幂等复用(reused=true 返回既有层,不重复建连)+ 落点校验(宁重连不错主机)。跳板传 jump(-J 不占层)。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "host": "<host>"
    },
    "name": "push_ssh"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo私钥文件路径(-i)
hostYes目标主机(user@host 或 ssh config 别名)
jumpNo跳板(-J:途径机不占层)
nameNo层名(缺省=host;注册表内唯一,显式寻址用)
portNoSSH 端口(非 22 时指定)
userNo登录用户名

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses idempotency at the same endpoint (reused=true returns the existing layer without reconnecting), endpoint validation semantics ('宁重连不错主机'), and that jump hosts do not consume a layer. What is not covered is failure behavior when connection or authentication fails, or what the returned layer object contains beyond the reused flag.

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?

Three short clauses, front-loaded with the establishing action, and each clause carries distinct information (default-layer role, idempotent reuse, jump routing). The heavy parenthetical nesting makes it dense to parse but nothing is redundant.

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?

For a 6-parameter connection-establishing tool with no annotations and no output schema, the description covers the important non-obvious behaviors: side effect of becoming the default layer, idempotent reuse, and jump handling. Gaps remain around authentication prerequisites and error outcomes, but the core call semantics are present.

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?

Schema description coverage is 100%, so every parameter already has documented meaning, including the jump note that appears in both places. The description reinforces the jump/layer interaction and the default naming, but adds little semantics beyond the schema, so the baseline 3 applies.

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 opens with a specific verb+resource: '建立命名 ssh 层' (establish a named ssh layer), and adds scope — it becomes the default layer that subsequent tools fall back to. That distinguishes it from siblings like push_into or run_command, which operate on existing layers, though it never names an alternative explicitly.

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?

Usage is implied rather than stated: the parenthetical '后续工具缺省落它' tells the agent this is the setup step before other tools, and the jump note tells it how to route through a bastion. There is no explicit when-not guidance or named alternative for the case where a layer already exists other than the idempotent-reuse note.

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