Termix MCP Server

connect_ssh_tunnel

Connect to a configured SSH tunnel by specifying tunnel name, source host ID, and tunnel index.

Instructions

Establish a configured SSH tunnel connection.

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": {
      "name": "<name>",
      "sourceHostId": "<sourceHostId>",
      "tunnelIndex": "<tunnelIndex>"
    },
    "name": "connect_ssh_tunnel"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Tunnel name
`tunnelIndex`	Yes	Index of the tunnel definition on that host
`sourceHostId`	Yes	ID of the source host the tunnel is defined on

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

C2.7/5.0

Behavior1/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action, without revealing side effects, idempotency, blocking behavior, error conditions, or what happens on success/failure. This is insufficient for a connection-establishing tool.

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?

The description is a single, front-loaded sentence with no wasted words. Every term ('Establish', 'configured', 'SSH tunnel', 'connection') contributes to the meaning.

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

Completeness2/5

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

The tool has no annotations and no output schema, and the description is minimal. It does not explain what the call returns, whether it is asynchronous, or what preconditions must be met. This is a significant gap for an action-oriented tool.

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 the baseline is 3. The description adds the nuance of 'configured' but does not further explain parameter relationships or usage beyond the schema's property descriptions.

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 uses the specific verb 'Establish' with the resource 'SSH tunnel connection', which clearly indicates the tool's action. It is implicitly distinct from the sibling 'disconnect_ssh_tunnel', though it does not explicitly differentiate itself.

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 guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., host must exist, tunnel must be configured), nor does it contrast with disconnect_ssh_tunnel or status tools.

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

Deploy Server