Skip to main content
Glama
remote-ssh-mcp
by RuiFG

ssh_reset_connection

Destructive

Resets a session's SSH connection to one host and revalidates its working directory to recover stale or broken sessions without replaying previous commands.

Instructions

Reset this session's connection to one host and revalidate its directory. Does not replay commands or guarantee termination of remote processes. Manually disconnected hosts require ssh_set_workspace instead.

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": {
      "hostId": "<hostId>"
    },
    "name": "ssh_reset_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostIdYesRequired stable host ID returned by ssh_list_hosts. Names are not accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag this as a destructive, non-idempotent, open-world operation; the description usefully adds that commands are not replayed and remote processes are not guaranteed to terminate, which bounds the blast radius. It still does not say what state is lost on the remote side or whether in-flight commands are interrupted.

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?

Three short sentences, front-loaded with the action and immediately followed by the negative guarantees and the alternative. No filler or restatement of the name.

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 single-parameter mutation with annotations and no output schema, the description covers action, side-effect boundaries, and the escape hatch to a sibling. Minor gap: it never says what a successful reset returns or how failure to reconnect surfaces.

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 hostId description already states it must be a stable ID from ssh_list_hosts and that names are not accepted. The tool description adds nothing about the parameter, so the baseline 3 applies.

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?

States a specific verb and resource: reset this session's connection to one host, plus the secondary effect of revalidating its directory. It also names the sibling it is not (ssh_set_workspace), so an agent can distinguish it without opening schemas.

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?

Explicitly routes manually disconnected hosts to ssh_set_workspace and clarifies the tool's scope, which gives clear use context. It does not state positive preconditions or timing (e.g., when a stale-but-connected session warrants a reset), so it falls short of full when/when-not/alternatives coverage.

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