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
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
binary_statusA

Report whether the patched Firefox binary is already cached locally.

Returns the cache path, version, and a ready flag. Does NOT download.

binary_installA

Download (and verify) the patched Firefox binary if not already cached.

One-time ~100 MB download, SHA256-verified. Set force=True to re-download even if a cached copy exists. Call this before session_start. Reports download progress (0-100%) when the server reports a size and the client supports progress tokens; phase changes (downloading/verifying/extracting) are always logged.

browser_startB

Start the agent browser; proxy and geo settings come from server config.

browser_statusA

Return status for the single agent browser; session_id is usually omitted.

browser_list_tabsB

List tabs in the agent browser and identify the active tab.

browser_activate_tabC

Switch the agent browser to an existing tab by page_id.

browser_stopB

Close the single agent browser; session_id is usually omitted.

browser_navigateC

Navigate and return no, compact, or full snapshot observation.

browser_reloadC

Reload and return no, compact, or full snapshot observation.

browser_snapshotC

Return a page snapshot and optionally match controls by query and role.

browser_click_refB

Click a ref from browser_snapshot and return the updated snapshot.

browser_set_value_refC

Fill a snapshot ref without echoing the value into the tool result.

browser_type_text_refC

Type into a snapshot ref without echoing the text into the result.

browser_select_option_refC

Select an option by snapshot ref and return the updated snapshot.

browser_set_form_valuesC

Fill several snapshot refs in one call; each item has ref and value.

browser_get_textC

Get paginated visible text from the single agent browser.

browser_find_textB

Find text in the active page and return short surrounding snippets.

browser_screenshotC

Capture the single agent browser; session_id is usually omitted.

browser_wait_forA

Wait until all supplied text, URL, and ref-state conditions are true.

text and url use case-insensitive substring matching. state is applied only when ref is supplied. At least one condition is required.

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

Disambiguation4/5

Most tools map to a clearly distinct action on the browser or binary. Minor overlap exists among content-extraction tools (browser_snapshot, browser_get_text, browser_find_text) and among input tools (browser_set_value_ref, browser_type_text_ref, browser_set_form_values), but descriptions differentiate them well enough that misselection is unlikely.

Naming Consistency4/5

The set is dominated by a consistent browser_verb_noun pattern, with action-oriented suffixes (click_ref, set_value_ref). The only deviation is the two binary_* tools, which themselves share a coherent verb_noun pattern, so the naming remains predictable overall.

Tool Count4/5

19 tools is slightly heavy but justified by genuine browser-automation breadth (lifecycle, tabs, navigation, interaction, extraction, waiting) plus binary management. Almost every tool covers a distinct capability, with little redundancy.

Completeness4/5

Core lifecycle (start/stop/status/reload/navigate), tab handling, form interaction, content extraction, waiting, and binary install/verify are covered, giving a nearly complete surface. Gaps remain for close-tab, keyboard/hover/scroll or drag actions, and cookie/download control, but agents can largely work around these.

Maintenance

ActivityStale
ResponsivenessNo issues