MCPGex
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_test_caseB | Add a test case for regex pattern validation. Each test case consists of an input string and the expected match/output. |
| test_regexA | Test a regex pattern against all current test cases to see if it satisfies the requirements. |
| get_test_casesA | Get all current test cases to see what requirements the regex pattern needs to satisfy. |
| clear_test_casesA | Clear all test cases to start fresh with new requirements. |
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 4 tools
Each tool has a distinct purpose: adding test cases, running tests, viewing test cases, and clearing them. There is no overlap or ambiguity between the four operations.
All tool names follow a consistent verb_noun pattern: add_test_case, test_regex, get_test_cases, clear_test_cases. The naming is uniform and predictable.
Four tools is well-scoped for a focused regex testing server. Each tool covers a necessary part of the workflow without redundancy or bloat.
The tool set covers the full lifecycle of regex test case management: add, view, test, and clear. There are no obvious gaps for the stated purpose.