ForgeQA AI
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_dom_accessibilityA | Open a supplied URL in a fresh headless Chromium session and return its accessibility tree as structured content. |
| dry_run_qa_flowA | Run role-based browser actions and assertions in a fresh headless Chromium session and return a step-by-step pass/fail report. |
| compile_playwright_specB | Write validated role-based browser actions and assertions to a Playwright spec in the local tests directory. |
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 3 tools
The three tools are largely distinct: one scans the accessibility tree, one executes a QA flow in the browser, and one writes a Playwright spec. dry_run_qa_flow and compile_playwright_spec both consume role-based actions and assertions, so an agent could initially confuse execution with persistence, but the descriptions clarify the difference.
All tool names follow a consistent snake_case verb_noun pattern: scan_dom_accessibility, dry_run_qa_flow, and compile_playwright_spec. The naming is predictable and action-oriented.
Three tools is a tight, well-scoped set for an AI-assisted QA server. Each tool maps cleanly to a distinct stage in the workflow: inspect, validate, and generate.
The core QA workflow is covered: accessibility scanning, flow verification, and spec generation. Minor gaps exist, such as no tool for listing or updating compiled specs, but these are workable for most use cases.