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": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
browser_openA

Start the one headed Chrome session and return the live view URL. Give that URL to the human: they can watch this exact session, and take over in it, while you drive. Safe to call twice — it reuses the session that is already open.

browser_navigateB

Navigate the session to an http(s) URL and return the page title, final URL and readable text. The server validates the destination and refuses blocked address classes.

browser_readA

Read the current page: title, URL, readable text and a bounded accessibility tree. Prefer this over a screenshot — it is structure, not pixels, and it does not spend a vision step unless you ask for the image.

browser_clickB

Click a CSS selector, or an x/y point in the viewport. Provide one, not both.

browser_typeA

Type text into a CSS selector, or at an x/y point. Text is sent byte for byte. Do not use this for a secret a human should enter — ask them to take over in the live view instead.

browser_pressC

Press one allowlisted key or combination. Allowed: Enter, Escape, Tab, Backspace, Delete, Space, ArrowUp, ArrowDown, ArrowLeft, ArrowRight, Home, End, PageUp, PageDown, Control+A, Control+Z, Control+Shift+Z, Meta+A, Meta+Z, Meta+Shift+Z.

browser_scrollC

Scroll the page by a nonzero pixel delta.

browser_statusA

Report whether the runtime is up, whether a session is open, how many vision steps remain, and the live view URL to hand to a human.

browser_closeA

End the session and release the browser. Idempotent. Call this when the task is finished so the single session slot is free.

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 9 tools

Disambiguation4/5

Each tool has a distinct purpose, but browser_open and browser_navigate could be confused since both initiate a session and navigate to a URL. The descriptions clarify the difference (open creates/reuses session, navigate goes to URL), but an agent might still misfire.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern with the 'browser_' prefix. This is predictable and readable.

Tool Count5/5

Nine tools is well-scoped for a browser automation server, covering essential actions like open, navigate, read, click, type, press, scroll, status, and close. No obvious bloat or missing core operations.

Completeness4/5

The surface covers the full browser lifecycle and common interactions (open, navigate, read, click, type, press, scroll, status, close). Minor gaps include no explicit wait or screenshot tool (though read can return an image), and no form submission or download handling, but these are workaroundable.

Maintenance

ActivityMaintained
ResponsivenessResponsive