zenpilot
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tabsA | List open tabs with ids. The active tab is marked with *. |
| new_tabB | Open a new tab (it becomes active), optionally loading url. |
| switch_tabC | Make a tab the active one. |
| close_tabC | Close a tab. |
| navigateB | Load url in a tab and wait for the page to finish loading. |
| read_pageA | Outline of the page's visible interactive elements and text. |
| clickA | Click an element by ref (from read_page) with a real mouse event. |
| typeA | Replace the content of a field (by ref) with text using real key events. |
| scrollC | Scroll the page with the mouse wheel by amount pixels. |
| screenshotC | Screenshot of the visible part of a tab. |
| get_textC | Readable main text of the page (prefers or a single ). |
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 11 tools
Most tools have clearly distinct browser-automation purposes, especially tab management and navigation versus interaction. The main overlap is read_page vs get_text, since both extract page content, but the descriptions distinguish interactive outline/refs from readable main text.
All names use snake_case and are generally readable and predictable. There are minor deviations: several tools are single verbs (type, click, navigate, scroll) and screenshot is a noun, so it is not a uniform verb_noun convention.
The 11 tools are well-scoped for a browser automation server. Each covers a distinct common browser operation, and the count is neither bloated nor too thin.
Core browser workflows are covered: read page, get text, click, type, scroll, screenshot, navigate, and tab management. Some useful operations are missing, such as hover, general key presses beyond typing/Enter, waiting for selectors, and retrieving the current URL, but agents can work around many of these.