bob-in-browser
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOB_BROWSER_OUT | No | Directory for full-resolution PNG screenshots. | $TMPDIR/bob-in-browser-shots |
| BOB_BROWSER_ENGINE | No | Default engine: `chromium`, `firefox`, or `webkit`. Overridable per call via `open_page`. | chromium |
| BOB_BROWSER_CDP_URL | No | Attach to a running Chrome at this CDP URL instead of launching one. E.g. `http://localhost:9222`. | |
| BOB_BROWSER_HEADLESS | No | Set to `false` to watch the browser work in a visible window. Useful when debugging a selector. | true |
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 |
|---|---|
| open_pageA | Open a URL in the browser and start capturing console + network errors. Call this first. Returns page title, HTTP status, and the active engine. Set |
| screenshotA | Capture the current page as an image so you can visually judge layout, spacing, and alignment. Also saves a full-resolution PNG to disk and returns its path. |
| check_responsiveA | THE core design check. Screenshots the page at several widths and runs a layout audit at each one, so you can see exactly which breakpoint breaks. Reports horizontal overflow, which is the most common responsive bug. |
| audit_designA | Run automated design and accessibility checks on the current page: horizontal overflow, tap targets under 44x44, WCAG AA text contrast, images missing alt, text under 12px, and content clipped by overflow:hidden. |
| read_consoleA | Read console messages and uncaught page errors captured since the last open_page. JS errors are the usual cause of a page that renders wrong. |
| read_network_errorsA | List failed requests and HTTP 4xx/5xx responses. Catches missing fonts, images, and stylesheets that silently degrade a design. |
| get_page_textA | Read the rendered text of the page, to check copy, hierarchy, and that content actually loaded. |
| interactA | Drive the page to reach a state worth inspecting: open a menu, submit a form, scroll to a section. Returns any new console errors the action triggered. Avoid elements that open native alert/confirm dialogs. |
| close_browserA | Close the browser and free resources. Call when the inspection is finished. |
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
Most tools have clear, distinct purposes, but check_responsive and audit_design both include horizontal overflow checks, which could lead to minor confusion. Overall descriptions are specific enough to tell them apart.
Most tool names follow a verb_noun snake_case pattern (check_responsive, read_console, open_page). Two deviations exist: 'screenshot' is a bare noun and 'interact' is a bare verb, but they still fit the general style.
9 tools is well within the ideal 3-15 range. Each tool covers a distinct inspection or interaction task, and none feel redundant or unnecessary for the server's browser auditing purpose.
The tool set covers the core workflow: open, inspect visually, check responsive/design/accessibility, read console/network, extract text, interact, and close. Minor gaps like explicit viewport resizing or element-level queries exist, but they are workaroundable.