Skip to main content
Glama

update_tunnel

Modify an existing saved SSH tunnel's name, port, target, type, or route, including team tunnels through a reachable host. Requires vault:edit.

Instructions

Change a saved tunnel (needs vault:edit; for a team's, through a host your access reaches).

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": {
      "tunnel": "<tunnel>"
    },
    "name": "update_tunnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
viaNo
kindNoChanging it to dynamic drops the target.
nameNo
portNo
targetNo
tunnelYesThe tunnel to change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full disclosure burden. It does disclose the required permission scope and the cross-team access path, but says nothing about update semantics: whether omitted parameters are preserved or cleared, whether a running tunnel is affected, or whether changes are reversible. For a mutation tool with zero annotation coverage this is a substantial gap.

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

Conciseness3/5

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

It is short and front-loads the core action, which is good. The parenthetical "for a team's, through a host your access reaches" is grammatically elliptical and ambiguous — the reader must guess what noun is being elided.

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?

Six parameters, a mutation operation, no annotations, and no output schema make this a case where the description should explain partial-update behavior and permission scope in detail. It covers only authorization and team scope, leaving the agent guessing about how field omission is interpreted and what the response contains.

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

Parameters2/5

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

Schema description coverage is 33% across six parameters, so the description needs to compensate and does not — it mentions no parameter by name and adds no meaning about name, port, target, or via. The one important behavioral note (switching kind to dynamic drops the target) lives in the schema, not the description.

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?

"Change a saved tunnel" gives a specific verb plus resource, and the word "saved" separates it from runtime siblings like start_tunnel and stop_tunnel without naming them. It stops short of distinguishing itself from add_tunnel/remove_tunnel in explicit terms, so it is clear but not maximally differentiated.

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 a precondition (vault:edit) and a team-access condition, which is genuine usage context. It never states when an agent should modify a tunnel versus stopping and recreating it, so selection guidance against siblings is only implied.

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