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

mcp-server-ssh

by atengk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ssh_session_close

Close a persistent interactive PTY terminal session to reclaim system resources.

Instructions

关闭指定的持久交互式 PTY 终端会话并回收系统资源

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": {
      "sessionId": "<sessionId>"
    },
    "name": "ssh_session_close"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes待关闭的 PTY 终端会话 ID

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 full behavioral disclosure. It states that the session is closed and resources reclaimed, but omits whether termination is graceful or abrupt, what happens to running processes, required permissions, error behavior, and whether the operation is irreversible.

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 redundant or filler content. It states the action and the resource immediately and ends cleanly.

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 one-parameter close tool with a fully described parameter, the description conveys the essential purpose and cleanup effect. However, with no annotations and no output schema, it should disclose more about side effects and safety to be fully complete for a destructive-style operation.

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 coverage is 100% and the single sessionId parameter is fully documented in the schema. The description adds no additional meaning, format, or constraints 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?

States a specific verb (关闭) and a precise resource (指定的持久交互式 PTY 终端会话), including a cleanup outcome (回收系统资源). It does not explicitly distinguish itself from siblings such as ssh_disconnect or ssh_session_send, so it falls short of a 5.

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?

No when-to-use guidance, prerequisites, or alternative tools are named. The usage is only implied by the action of closing a session; there is no explicit context for choosing this tool over ssh_disconnect or other session or connection operations.

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