Testing Bank MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_environmentsA | List all available testing environments in the Testing Bank |
| detect_environmentB | Automatically detect which environment to use based on a customer issue description |
| connect_environmentC | Connect to a specific testing environment sandbox |
| disconnect_environmentB | Disconnect from a testing environment |
| get_active_environmentsB | Get list of currently connected environments |
| route_to_environmentB | Send a command to a connected environment. Use this to execute tools in the child environment. |
| smart_routeA | Automatically detect the right environment from issue description and connect to it |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Tools are mostly distinct, but detect_environment and smart_route have overlapping purposes (detecting vs detecting+connecting), which could cause some confusion. Other tools clearly cover different actions.
Six tools follow verb_noun snake_case pattern (e.g., connect_environment, list_environments). smart_route deviates by starting with an adjective instead of a verb, breaking the pattern slightly.
With 7 tools, the set is well-scoped for managing testing environments: connect, detect, disconnect, list, route, and smart route cover essential operations without bloat.
The tool surface covers core lifecycle (connect, disconnect, list, interact) and adds detection features. Missing environment creation or modification, but those may be out of scope for a testing bank server.