ZeroDOM
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zerodom_parse_urlA | Navigate to a URL and return its interaction graph. Returns the compact text graph: Set frames=True when the controls you need are inside an iframe — embedded editors, payment fields, consent gates. Off by default because it costs a read per frame and most frames on a commercial page are advertising. |
| zerodom_read_pageA | Re-read the current page without navigating. Use after an action changed the page, or when node ids look stale. Unlike zerodom_parse_url this does not reload, so anything typed into the page stays. |
| zerodom_findA | Search the current page's graph for nodes matching Case-insensitive substring match over each node's label and type. Prefer this over re-reading the whole page when you already know what you are looking for: "checkout" costs three lines, the full graph costs every node on the page. |
| zerodom_click_nodeA | Click a node and return what changed on the page. Returns a diff — |
| zerodom_fill_nodeA | Type text into a node and return what changed on the page. The text is echoed back in the first line; the diff below it reports structural change — a validation error appearing, an autocomplete list opening. |
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 5 tools
Each tool targets a distinct action: navigation, reading, searching, clicking, and filling. No overlap in purpose; descriptions clearly differentiate their use cases.
All tools follow a consistent zerodom_verb_noun pattern (click_node, parse_url, read_page, find, fill_node). Naming is predictable and uniform, making the set easy to navigate.
Five tools is well-scoped for a DOM interaction server, covering core navigation, reading, searching, and action tasks without redundancy or bloat.
The tool surface covers the full lifecycle: navigating to a page, reading current state, searching within it, and performing actions (click, fill). No obvious dead ends or missing essential operations for the stated purpose.