Skip to main content
Glama

start_tunnel

Opens a saved SSH tunnel by name for agent use, enabling traffic forwarding to approved hosts without exposing passwords or keys.

Instructions

Start a saved tunnel (needs the tunnels scope on its host).

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>"
    },
    "name": "start_tunnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesIts name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavioral burden and largely doesn't. It never says what starting actually does (e.g. opens a forwarded port, spawns a process), whether the call is idempotent if the tunnel is already running, or whether the effect is persistent across sessions. Only the required OAuth scope is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler, and the scope requirement is tucked into a parenthetical rather than cluttering the main clause. It is efficient, though the brevity is part of the under-specification problem rather than purely a virtue.

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?

This is a state-changing operation with no annotations, no output schema, and only one parameter, so the description is the sole source of behavioral context — and it omits what the call does, what failure modes exist (unknown name, no such scope), and what is returned. It is not enough for an agent to invoke this confidently.

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 there is a single parameter, so the schema already explains `name`. The description's only added nuance is the word "saved", hinting the name refers to a previously persisted tunnel rather than an ad-hoc one; that is marginal at best.

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 resource ("Start a saved tunnel"), which cleanly separates it from the sibling operations on tunnels (stop_tunnel, add_tunnel, remove_tunnel). It does not explicitly name a sibling, but the action/state-change is unambiguous.

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?

The only guidance is a prerequisite ("needs the tunnels scope on its host"), which is auth/setup context rather than when-to-use guidance. Nothing says when to prefer this over add_tunnel or open_session, or what condition must hold (e.g. tunnel exists and is stopped) before starting.

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