Glance
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BROWSER_CHANNEL | No | Browser channel (e.g., chrome, msedge) | |
| BROWSER_TIMEOUT | No | Default timeout in ms | 30000 |
| BROWSER_HEADLESS | No | Run browser in headed mode | true |
| BROWSER_SESSIONS_DIR | No | Directory for screenshots and sessions | .browser-sessions |
| BROWSER_VIEWPORT_WIDTH | No | Browser viewport width | 1280 |
| BROWSER_VIEWPORT_HEIGHT | No | Browser viewport height | 720 |
| BROWSER_SECURITY_PROFILE | No | Security profile (local-dev, restricted, open) | local-dev |
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
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 32 tools
Tool names are mostly distinct, with browser_* and test_* prefixes clearly separating categories. However, some potential overlap exists between browser_screenshot and browser_snapshot, and test_fill_form could be confused with browser_type. Overall, the names are specific enough for an agent to differentiate.
All tools follow a consistent pattern of prefix_object_action (e.g., browser_navigate, test_scenario_run, session_start). This uniformity makes the set predictable and easy to navigate.
With 32 tools, the count is high but appropriate for a comprehensive browser automation and testing server. Each tool seems justified given the domain (browser control, testing, sessions, visual checks), though a slight reduction could improve simplicity.
The tool surface covers major browser interactions, testing scenarios, session management, and visual comparisons. Missing elements like network mocking or cookie management are notable, but core workflows appear well-supported.