Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGENTGO_EXENoPath to the AgentGo executable to use instead of starting `agentgo` from PATH

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
browser_openA

Go to a URL (or search Google with plain words), wait for the load, and return the page as a compact outline: headings plus interactive elements as [ref] role "name". Use the refs with browser_act.

browser_readA

Read the current page. view: page (outline with refs, default), text (readable content, text boxes and code included), links, forms, tables, meta. filter keeps matching lines; offset and max count lines.

browser_actA

Act on an element by ref with real input, wait for the page to settle, and get back only what changed. action: click, fill (text), press (key), check, uncheck, select (value, or values for a multiple list), hover, scroll (to: top|bottom, or ref; until: a text to scroll to, in the page or ref's list), type (text at focus), upload (paths). Add submit:true to fill to press Enter; expect {gone, shows, enabled, url, changes} must hold after, or it fails. If the reply is approval.required or handoff.required, call browser_wait_human.

browser_batchA

Run several browser_act steps in order in one call (e.g. fill a whole form and click Save; {action:"wait", ms} pauses). Stops at the first failure. Returns the final change set.

browser_waitA

Wait until text appears, a selector is visible, a selector or text is gone, the URL contains a string, or ref enabled is usable; returns what changed. ms: just pause. No condition: waits for load.

browser_tabsC

Manage your tabs. op: list, new (url), switch (tabId), close (tabId), back, forward, reload.

browser_screenshotA

Screenshot the page (or one element by ref) and return the image. Costs many tokens: prefer browser_read unless you need to see layout, images or a canvas.

browser_wait_humanB

Wait for the human operator: pass approvalId after approval.required, or nothing after handoff.required (CAPTCHA, login). Never try to solve a CAPTCHA yourself.

browser_guideA

How to use this browser, when you are unsure. topic=start: the loop, rules that save turns, errors (short). topic=skill: the full guide. topic=commands: find commands: pass query (words, e.g. "selector click") for the matching ones, or group for one section (open, read, act, batch, accounts, person, browser; all = every command, about 25,000 tokens). topic=gomini: GoMini, the optional local model that takes routine steps, and how to phrase subgoals for it.

browser_accountA

Use the accounts the person linked for you in the Account Center. op=accounts lists them (linked or not); op=apis lists the APIs you can call; op=call sends one API request as the account (connector, method, path, body) without you ever holding a token; op=sign_in has the browser type the saved sign-in into the current page's login form. If an account is not linked you get policy.denied: ask the person to link it, do not work around it.

browser_callB

Call any other AgentGo protocol method directly (cookies, downloads, PDF, dialogs, network log, workflow.collect ...). browser_call {method:"browser.capabilities"} lists them.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 11 tools

Disambiguation4/5

Most tools have clearly distinct purposes: reading, acting, waiting, navigation, screenshots, tabs, accounts, and human handoff are separable. Minor overlap exists between browser_act and browser_batch (batch runs multiple acts), between browser_open and browser_tabs op=new (both can open a URL), and browser_call acts as a wildcard that could duplicate any dedicated tool.

Naming Consistency4/5

All tool names use a consistent browser_ prefix and snake_case, making the set easy to scan. The only minor inconsistency is that some names are verb-led (browser_read, browser_act) while others are noun-led (browser_tabs, browser_account), but the pattern remains predictable.

Tool Count5/5

Eleven tools is well within the typical 3-15 range and each tool covers a meaningful part of browser automation. The set avoids redundancy while still offering specialized tools like batch, wait_human, and account handling.

Completeness5/5

The surface covers the full browser lifecycle: open/navigate, read, act, batch actions, wait, screenshot, tab management, accounts, and human handoff. browser_call provides a documented escape hatch for any protocol method not exposed as a dedicated tool, so there are no obvious dead ends.

Maintenance

ActivityNo data
ResponsivenessSyncing