cool-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 |
|---|---|
| cooltest_init_suiteA | Generate a .cooltest JSON from a test case source (first step of the flow, used for "Use Cool Test for"). Does not overwrite an existing suite by default; returns skipped. Set overwrite=true to rebuild. Call this to create the suite, then append cases with cooltest_update_case. |
| cooltest_list_suitesA | List existing suites under the project root .cooltest (name/filePath/caseCount/updatedAt). Call first to see which suites exist when working with multiple suites. |
| cooltest_list_casesA | List case summaries for a suite (id/title/status/priority), without steps/evidence to save tokens. Call before testing to get an overview. |
| cooltest_get_caseA | Read a single case's full content (including steps/expected/evidence). Use by id when testing case by case. |
| cooltest_update_caseA | Update a case's status/notes/evidence/lastRunAt. Write back results after testing; set status to review with a required notes reason when a case cannot be tested or judged. Also used to append new cases after init (provide the full field set each time). |
| cooltest_get_statsA | Suite status statistics (total/passed/failed/review/pending). Use to report progress after testing. |
| cooltest_open_reportA | Start the local report server (zero-dependency Node single script) and open the visual report page in a browser. Call after testing finishes. Returns the url and port. |
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 has a distinct purpose: listing suites vs listing cases, reading a case vs updating it, getting stats, and opening the report. No overlap or ambiguity between tool responsibilities.
All tools follow the consistent pattern cooltest_verb_noun (list_cases, get_case, update_case, get_stats, open_report, init_suite, list_suites). The prefix and snake_case naming are uniform throughout.
Seven tools cover the core workflow of initializing, listing, reading, updating, and reporting on test suites. This is a well-scoped set without redundancy or bloat.
The tools form a complete lifecycle: init_suite creates a suite, list_suites shows existing ones, list_cases/get_case allow reading, update_case supports writing (including appending cases), get_stats provides status, and open_report produces the final output. No obvious missing operations for the intended workflow.