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
browser_navigateB

Navigate to an absolute HTTP(S) URL and return a marked viewport.

browser_click_markB

Click an element from the latest Set-of-Marks snapshot.

browser_scrollA

Scroll the active viewport up or down and return a fresh snapshot.

browser_session_createD
browser_session_closeD
browser_tabsD
browser_snapshotD
browser_actD
browser_extractD

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.9/5.0

Scored across 9 tools

Disambiguation2/5

Several tools have unclear or missing descriptions. browser_act, browser_snapshot, and browser_extract overlap in purpose without clear boundaries. The generic 'act' could subsume click_mark or scroll, and 'snapshot' may duplicate the marked viewport from navigate.

Naming Consistency3/5

All tools share the 'browser_' prefix, which is good, but the second part mixes verb phrases (navigate, click_mark, scroll) with noun phrases (tabs, snapshot). 'browser_act' is too vague and breaks the more descriptive pattern.

Tool Count4/5

9 tools is a reasonable size for a browser automation server. The count is not excessive and covers major browsing actions, though some tools could be consolidated.

Completeness3/5

The server covers core browsing actions like navigation, clicking, scrolling, session management, and tabs. However, there are potential gaps such as form fill, back/forward, or wait operations, and the generic 'act' and 'extract' tools leave it unclear whether those capabilities are fully addressed.

Maintenance

ActivityMaintained
ResponsivenessNo issues