Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

getTunnelList

List active TestingBot tunnels and their identifiers to run tests against local or firewalled sites.

Instructions

Get a list of all active TestingBot tunnels on the account, with their identifiers. Tunnels allow you to test websites behind firewalls or on your local machine.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the whole burden, and it does disclose two meaningful traits: the result is account-scoped and restricted to currently active tunnels. It does not state whether the call is read-only in effect, how results are ordered or bounded, or what authentication/account context is required.

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 short sentences, front-loaded with the operation and scope, with the second sentence spending its words on defining the domain term 'tunnel'. Nothing is redundant, though the explanatory sentence is only marginally necessary for an agent.

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 zero-parameter, read-oriented list tool without an output schema, the description covers scope (active only, account-wide) and the key returned field (identifiers). The main remaining gap is the absence of any statement about non-active tunnels or result ordering/limits.

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?

The tool takes zero parameters and additionalProperties is false, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly makes clear no filtering inputs are accepted.

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?

The description gives a specific verb and resource ('Get a list of all active TestingBot tunnels on the account') plus the payload ('with their identifiers'), and the second sentence explains what a tunnel is. It does not explicitly contrast with startTunnel/stopTunnel/deleteTunnel, so it falls short of full sibling differentiation.

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: an agent can infer this is the discovery call before stopping or deleting a tunnel, since only 'active' tunnels are returned. There is no explicit when-to-use statement, no mention of a related alternative such as listing inactive or historical tunnels, and no prerequisites or caveats.

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