Skip to main content
Glama

remove_tunnel

Deletes a saved SSH tunnel by name, stopping it first if active, and requires vault edit permission plus access to its host.

Instructions

Remove a saved tunnel (needs vault:edit; for a team's, through a host your access reaches). A tunnel you started is stopped first.

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": "remove_tunnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesIts name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations at all, the description still discloses a genuine side effect (a running tunnel is stopped before removal) and the required permission scope. It omits irreversibility, behavior when the name doesn't exist, and any confirmation requirement, which keeps it short of full coverage.

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?

Two sentences, no filler, with the action stated first and the side effect second. The parenthetical "for a team's, through a host your access reaches" is elliptical to the point of ambiguity and slightly burdens parsing.

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 one-parameter deletion tool with no output schema, the definition covers auth scope and the stop-before-remove side effect, which is what an agent needs to call it. Missing failure semantics (name not found, permission denied response) are the only real gap.

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

Parameters5/5

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

One parameter with 100% schema description coverage, so the schema already defines "name"; the description correctly avoids redundant parameter exposition. No additional meaning is needed for a single required string identifier.

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 ("Remove") and resource ("saved tunnel"), and the closing line about stopping a started tunnel first implicitly separates it from stop_tunnel. It never names a sibling explicitly, so it stops 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The parenthetical supplies real prerequisites — vault:edit permission and reachability of the host backing a team's tunnel — which is more than most mutations offer. However, it never says when to prefer remove_tunnel over stop_tunnel or update_tunnel, leaving the permanent-vs-temporary distinction for the agent to infer.

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