tuxedo-qa
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 |
|---|---|
| create_test | Create a new Playwright test file. Generate the full test code and pass it here. |
| list_tests | List all test files with their last known status. Supports filtering by status and limit. |
| read_testC | Read the contents of a test file. |
| update_testB | Update a test — script, display name, description, schedule, or enabled state. |
| delete_testA | Permanently delete a test and its history. Irreversible — prefer update_test with enabled: false to deactivate. |
| run_tests | Run all tests or a specific test file. Respects pause state. Sends a webhook notification if one is configured. |
| run_until_passB | Run a test repeatedly, applying automatic fixes on each failure, until it passes or max attempts is reached. |
| get_statusA | Get overall suite status, or per-test status with failure details and fix suggestion when test_name is provided. |
| pause_testsA | Pause all tests for up to 60 minutes. Tests resume automatically. Use before deploys to avoid false alerts. |
| set_webhook | Configure a webhook URL (Discord, Slack, or a generic JSON endpoint) for test notifications. |
| create_credential | Create or update a named credential set (e.g. admin, user_comum). Fields are key-value pairs like { email, password, token }. |
| list_credentials | List all saved credential sets with masked values. |
| delete_credentialC | Delete a named credential set. |
| start_pair_debugA | Start a pair-debugging session: opens a visible browser at the given URL for the human to drive by hand. Records console messages, network errors, page exceptions, navigations, and their clicks/fills with timestamps as they go, so you can correlate what they did with what broke. Use when the user wants to walk through a flow live and have you spot the bug, rather than writing a scripted test upfront. |
| get_pair_debug_contextA | Get the recorded timeline of the active pair-debugging session so far (console, network, errors, navigations, actions). Call this whenever the user says something looks wrong, to see exactly what just happened. |
| stop_pair_debug | End the active pair-debugging session: closes the browser and returns the full recorded timeline plus a draft Playwright test built from the actions the human performed. Save it for real with create_test if it holds up. |
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 9 tools
Each tool targets a distinct resource or action: credentials, tests (CRUD except create), debugging sessions, status, and pausing. No overlapping purposes.
Most tools follow verb_noun pattern (e.g., delete_test, get_status). 'run_until_pass' deviates slightly as a verb phrase, but overall convention is consistent and clear.
9 tools is well-scoped for a test management server, covering operations like test editing, debugging, status checks, and credential management without excess.
Missing a create_test tool, which is a notable gap for full lifecycle management. Also lacks a simple 'run test' command independent of the auto-fix loop. However, debugging features are well-covered.