Skip to main content
Glama

stop_tunnel

Terminates a tunnel you started by name, closing the forwarded connection to your server when it is no longer needed.

Instructions

Stop a tunnel you started.

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

Input Schema

NameRequiredDescriptionDefault
nameYesIts name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly fails to: it does not say whether stopping is graceful, whether the tunnel definition survives for a later start, whether it errors when the tunnel is not running, or what permissions are needed.

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 short, front-loaded sentence with a clear verb and no wasted wording. It is arguably too sparse rather than too verbose, but nothing in it is redundant.

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

Completeness3/5

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

For a one-parameter lifecycle tool with no output schema and no annotations, the description is minimally sufficient to call it with a name. It leaves unresolved what state change actually occurs and how it differs from the coexisting remove_tunnel, which is the main completeness gap.

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?

There is a single required parameter with 100% schema description coverage, so the schema already defines it and the baseline applies. The description's "you started" qualifier hints that name refers to the caller's own tunnel, but adds no format or resolution detail beyond the schema.

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 ("Stop a tunnel") with an ownership qualifier ("you started"), which the agent can act on directly. It does not distinguish stopping from removing a tunnel, so an agent facing both stop_tunnel and remove_tunnel has no stated basis for choosing.

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?

Usage is only implied: stop a tunnel that you started, i.e., one currently running. There is no explicit when-to-use statement, no mention of what to do if the tunnel is already stopped, and no pointer to a sibling for the delete-vs-stop case.

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