Decide Test 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 |
|---|---|
| parse_decision_tableB | Parse a decision table from CSV, JSON, or Markdown format and generate test case specifications |
| get_web_test_guidanceB | Get guidance and example steps for planning web tests. Returns structured information to help Claude plan test steps for a web application flow. |
| execute_web_testB | Execute predefined web test steps using Playwright. Takes a test case and specific steps to execute. |
| get_api_test_guidanceB | Get guidance and example steps for planning API tests. Returns structured information to help Claude plan API test steps. |
| execute_api_testC | Execute predefined API test steps. Takes a test case and specific API steps to execute. |
| generate_test_codeB | Generate executable test code (Playwright or API tests) from test cases and steps |
| run_generated_testsC | Execute generated tests and return results |
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
Each tool targets a specific function: API vs web execution, guidance, parsing, code generation, and test execution. No two tools have overlapping purposes, ensuring clear selection.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., execute_api_test, get_web_test_guidance). The naming is predictable and uniform throughout.
With 7 tools, the server covers the essential testing workflow without being too sparse or bloated. Each tool serves a necessary role in planning, generating, or executing tests.
The tool set covers the main lifecycle: guidance for planning, parsing decision tables, generating code, and executing tests. Minor gaps like persistent test case storage or advanced reporting exist but are not critical for the core workflow.