Skip to main content
Glama
Sign In
mcp-server-ssh

mcp-server-ssh

by atengk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ssh_disconnect

Close a specified SSH connection by connection ID to free resources and end the remote session. Use it when you need to terminate an active connection cleanly.

Instructions

断开并关闭指定的 SSH 物理网络连接

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": {
      "connectionId": "<connectionId>"
    },
    "name": "ssh_disconnect"
  }
}

Input Schema

NameRequiredDescriptionDefault
connectionIdYes待关闭的 SSH 连接标识符

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.5

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states that a connection is closed but omits whether the connection must be active, what happens on failure, whether the operation is reversible, or any side effects on sessions tied to the connection.

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?

A single, front-loaded sentence with no wasted words that names the action and its target directly.

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

Completeness3/5

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

For a simple one-parameter tool with no output schema this is minimally adequate, but with no annotations and no differentiation from ssh_session_close, an agent lacks enough context to choose confidently between the two.

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% and the single connectionId parameter is fully documented in the schema. The description adds no meaning beyond what the schema already provides, so the baseline of 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 gives a specific verb pair (断开/关闭) and resource (指定的 SSH 物理网络连接), making the operation clear. It does not, however, differentiate itself from the sibling ssh_session_close, which an agent could easily confuse with closing a connection.

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

Usage Guidelines2/5

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

There is no explicit statement of when to use this tool versus alternatives such as ssh_session_close or when not to call it. Usage is only implied by the tool name and verb.

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