Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BU_CDP_URLNoThe URL of the Chrome DevTools Protocol endpoint.http://127.0.0.1:9222

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
jevbrow_openA

Open an http(s) URL in a Jev-owned background tab in the local browser.

jevbrow_observeA

Read the current URL, visible text, and supported actions before acting.

jevbrow_clickA

Click one observed action with its fingerprint, then inspect the new state.

jevbrow_type_textA

Type into one observed field. Inspect the new state before acting again.

jevbrow_selectA

Select one observed native dropdown option by action_id; never accepts model-generated selectors or values.

jevbrow_scroll_or_waitA

Execute one observed scroll or wait action by action_id, then return a fresh observation.

jevbrow_closeA

Close only the background tab opened and owned by Jev; does not close the user's other browser tabs.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct browser interaction: open, observe, click, type, select, scroll/wait, and close. Even though scroll_or_wait and observe both return observations, their triggering actions are clearly differentiated and never overlap.

Naming Consistency5/5

All tools share a consistent jevbrow_ prefix and use clear imperative verb phrases like open, observe, click, type_text, select, and close. The naming pattern is predictable and easy to reason about as a unified set.

Tool Count5/5

Seven tools is well-scoped for a browser automation toolset, covering the full lifecycle from opening a tab to observing state, performing actions, and closing the tab. There is no redundancy or bloated surface area.

Completeness4/5

The set covers the essential browser automation loop: open, observe, click, type, select, scroll/wait, and close. Minor gaps like explicit back/forward navigation or refresh are absent, but they are likely accessible through observed clickable actions.

Maintenance

ActivityMaintained
ResponsivenessNo issues