Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

stopTunnel

Stop a TestingBot Tunnel started by this MCP server by identifier or stop all launched tunnels to end local/private site access and release resources.

Instructions

Stop a TestingBot Tunnel that was started with startTunnel. Without a tunnelIdentifier, stops the only one running (or all of them with all: true). For tunnels started outside this MCP server, use deleteTunnel.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stopTunnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoStop every tunnel this MCP server started
tunnelIdentifierNoIdentifier returned by startTunnel

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the key behavioral trait: omitting tunnelIdentifier silently targets the sole running tunnel, and all:true widens that to every tunnel this server started. It does not state what happens when several tunnels are running and neither parameter is given (error vs. arbitrary pick), nor whether the stop is immediate or graceful, which leaves a meaningful edge case undisclosed.

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?

Three short sentences, front-loaded with the action, then the default case, then the sibling routing. Every sentence carries information and nothing is padded.

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 two-parameter, no-output-schema tool this is nearly complete: action, defaults, and the alternative tool are all covered. The only real omission is the outcome when multiple tunnels are running with no selector, which matters for predicting whether the call succeeds.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description goes beyond the schema by explaining the interaction of the two parameters — that tunnelIdentifier suppresses the default behavior and that all:true is the explicit widening of that default. That is genuine added meaning rather than a restatement of the property descriptions.

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?

States a specific verb and resource ("Stop a TestingBot Tunnel") and immediately ties it to the tool that creates those resources (startTunnel). It also names the sibling deleteTunnel and the scope difference, so an agent can distinguish it from both alternatives without opening any schema.

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?

Gives explicit routing conditions: use this for tunnels started by startTunnel, use deleteTunnel for tunnels started outside this MCP server. It also documents the default behavior when tunnelIdentifier is omitted, so no inference is required to choose the right tool or invocation shape.

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