Skip to main content
Glama
Sign In
Remote SSH MCP

Remote SSH MCP

by the-nine-nation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Interrupt SSH foreground command

ssh_interrupt
Destructive

Send Ctrl-C to interrupt the foreground process in a remote SSH session and wait for shell recovery, keeping the session only after confirmation. Returns a status when idle.

Instructions

Send Ctrl-C to the current foreground process group and wait for the shell protocol to recover. The session is kept only when recovery is confirmed. Returns nothing_to_interrupt when idle.

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": {
      "id": "<id>"
    },
    "name": "ssh_interrupt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior5/5

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

Discloses that the session is kept only when recovery is confirmed and that it waits for recovery, going beyond the destructiveHint annotation. Reveals return behavior for idle state.

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?

Two sentences, direct, no redundant words, front-loads the primary action.

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?

Covers the main behavior and idle return, but omits how the id parameter relates to the session and lacks error cases beyond idle. Given simple schema and no output schema, it's mostly sufficient.

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

Parameters1/5

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

Schema coverage is 0% and description never explains the required 'id' parameter. The agent cannot learn from the description what id identifies or how to obtain it.

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?

Clearly states it sends Ctrl-C to the current foreground process group, distinguishing it from open/run/peek/list/close siblings. Specific verb 'send' and resource 'foreground process group'.

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?

Describes the recovery wait and the 'nothing_to_interrupt' when idle, which guides when it's applicable. Does not explicitly name alternatives but context implies interrupt vs other session 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