ego-webqa
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EGO_WEBQA_HTTP_PASSWORD | No | Password for HTTP Basic authentication when auditing authenticated previews. | |
| EGO_WEBQA_HTTP_USERNAME | No | Username for HTTP Basic authentication when auditing authenticated previews. | |
| EGO_WEBQA_EXTRA_HTTP_HEADERS | No | JSON object string of extra HTTP headers to send when auditing authenticated previews, e.g. {"X-Preview-Key":"agent-key"}. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_web_pageA | Audit a generated page in a real browser and return deterministic evidence. Provide exactly one of |
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 1 tool
With only one tool, there is no possibility of selecting the wrong tool or confusing overlapping purposes. The single tool's intent is explicit and self-contained.
The lone name `audit_web_page` follows a clear verb_noun snake_case convention. There are no competing names to create inconsistency.
A single tool is thin, but it matches the server's narrow, focused purpose of auditing a generated web page in a real browser. It is slightly under-scoped rather than bloated.
The audit operation itself is well-covered and explicitly bounded (delivery usability, not security/WCAG/visual regression/Safari parity). However, there are no supporting operations such as listing past audits, batch auditing multiple pages, or managing the referenced JSON config, leaving some workflow dead ends.