Skip to main content
Glama
Sign In
rustunnel-mcp

rustunnel-mcp

by joaoh82
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Remote

close_tunnel

Force-close a specific tunnel by its ID to instantly stop its public URL. Use after a webhook test or demo ends.

Instructions

Force-close a specific tunnel by its ID. The public URL stops working immediately. Use this when a tunnel is no longer needed or public access must be revoked right away — e.g. after a webhook test or demo finishes. Use list_tunnels to find the tunnel_id.

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_id": "<tunnel_id>"
    },
    "name": "close_tunnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoAPI token. Optional if RUSTUNNEL_TOKEN is set.
tunnel_idYesUUID of the tunnel to close

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Discloses that 'The public URL stops working immediately', which is a key behavioral trait. However, with no annotations, it doesn't mention irreversibility or potential side effects. Still, it provides important context beyond the schema.

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?

Four sentences, front-loaded with core action, then effect, then usage context, then sibling reference. No unnecessary words; every sentence adds value.

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 simple tool with 2 params and no output schema, the description covers purpose, effect, and usage hints. Could explicitly mention that the action is irreversible or idempotent, but overall it's sufficient.

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%, so baseline is 3. The description adds 'by its ID' and 'use list_tunnels to find the tunnel_id', but doesn't add significant new meaning about parameters beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Force-close a specific tunnel by its ID', which is a specific verb and resource. It distinguishes from sibling tools like create_tunnel and list_tunnels by providing usage context and referencing list_tunnels for finding the ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly states when to use: 'when a tunnel is no longer needed or public access must be revoked right away' with examples (webhook test, demo). Also directly recommends an alternative tool 'Use list_tunnels to find the tunnel_id'.

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

Deploy Server

Other Tools