Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
tabs_contextA

List the tabs in the focused Zen window (tabId, title, URL, which is active). Call this first to get tab ids.

tabs_createB

Open a new tab (optionally at a URL) and make it active. Returns its tabId.

tabs_closeC

Close a tab.

tabs_selectC

Switch to (activate) a tab.

navigateA

Navigate a tab to a URL and wait for it to load. Pass "back" or "forward" to move through history.

screenshotB

Capture the visible part of a tab as an image. The tab is brought to the front first.

computerB

Mouse and keyboard actions in a tab. Click actions take either a coordinate (from the latest screenshot) or a ref. Actions: left_click, right_click, double_click, triple_click, hover, type (text into the focused element), key (space-separated keys like "Enter", "ctrl+a", "Backspace Backspace"), scroll, scroll_to (ref), wait, screenshot, zoom (region of the screenshot at higher detail).

read_pageA

Read the page as an accessibility-style tree. Interactive elements are tagged [ref_N] for use with computer/form_input.

findB

Find elements whose role, accessible name or text contains the query (case-insensitive). Returns up to 20 refs.

form_inputB

Set the value of an input, textarea, select, checkbox/radio or contenteditable element by ref.

get_page_textC

Extract the readable text of the page (main/article content first).

javascriptA

Run JavaScript in the tab and return the value of the last expression (top-level await works). Runs in the extension's isolated world with full DOM access; reach page globals via window.wrappedJSObject. Return JSON-able values. For debugging and inspection, not for faking user input.

read_console_messagesC

Read console output (log/info/warn/error/debug and uncaught errors) captured from the tab.

read_network_requestsB

List network requests made by the tab since the extension started watching it.

resize_windowC

Resize the Zen window containing the tab.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 15 tools

Disambiguation4/5

Most tools target clearly distinct actions: tab lifecycle (tabs_*), navigation, page reading, element finding, form input, JS eval, console/network reading. The main overlaps are the standalone screenshot tool versus computer's built-in 'screenshot'/'zoom' actions, and read_page vs get_page_text vs find, which require reading descriptions to separate. These are minor and descriptions do disambiguate, but an agent could still occasionally reach for the wrong page-reading tool.

Naming Consistency3/5

The tabs_* group is consistent but uses noun_verb order (tabs_create, tabs_close) while other tools use verb_noun (get_page_text, read_page, resize_window) or bare nouns/verbs (screenshot, navigate, computer, javascript, find). It's readable and mostly self-explanatory, but two conflicting conventions coexist with no unifying scheme.

Tool Count5/5

15 tools is well within a healthy range for a browser-automation server, and each tool maps to a meaningful capability (tab management, interaction, inspection, diagnostics). Nothing feels redundant enough to cut, and no obvious gap-forcing consolidation is needed.

Completeness4/5

The surface covers the full browser workflow: tab lifecycle, navigation with history, screenshots, DOM reading, element search, form filling, JS execution, console and network diagnostics, and window resizing. Minor gaps exist—no drag-and-drop action in computer, no cookie/localStorage or download management, and no explicit reload—but agents can work around these via javascript or navigate.

Maintenance

ActivityNo data
ResponsivenessOutdated data