Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NODE_OPTIONSNoOptional Node.js runtime options. Set to "--use-system-ca" when running behind a corporate network or proxy on Windows.

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

Tools

Functions exposed to the LLM to take actions

NameDescription
open_pageA

Open a URL or local file path in the browser and return page metadata, final URL, HTTP status, and viewport dimensions.

navigate_backB

Navigate back to the previous page in the browser session history.

navigate_forwardB

Navigate forward to the next page in the browser session history.

reload_pageC

Reload the currently active page in the browser.

inspect_pageB

Inspect the currently opened page, returning document/viewport dimensions, landmarks, heading hierarchy, images, links, buttons, and forms with accessibility notices.

inspect_elementB

Inspect a specific DOM element using a CSS selector. Returns tag, text, attributes, computed styles, bounding box, visibility, parent, and relevant children.

inspect_stylesA

Inspect computed CSS styles and box model (display, position, width/height, margin, padding, flex/grid, overflow, z-index, font-size) for a selector.

inspect_page_structureB

Return a clean, readable structural hierarchy of the page DOM focusing on semantic elements (header, nav, main, section, footer, headings) up to max_depth.

test_responsivenessA

Test a webpage across standard or custom viewport sizes (320px mobile to 1920px desktop). Detects horizontal overflow, clipped content, broken navigation, and overlapping elements at each size, captures screenshots, and returns structured findings.

detect_overflowB

Identify horizontal page overflow, elements wider than their containers, content extending beyond viewport boundaries, fixed-width hazards, media overflow, and clipped text.

inspect_breakpointsA

Inspect how layout transforms across viewport widths (320px to 1920px). Probes navigation shifts, grid/column count changes, and discovers declared CSS @media queries.

inspect_element_responsivenessB

Track a specific element (e.g. hero section, nav bar, image, card grid, or button) across multiple viewports to analyze how its bounding box, font-size, layout model, and padding scale.

compare_viewportsB

Capture screenshots of a webpage across mobile (375px), tablet (768px), and desktop (1440px) viewports, identify structural layout shifts, and compute visual pixel diff analysis.

capture_screenshotC

Capture a viewport, full-page, or specific element screenshot and save it to the output directory with metadata.

audit_layoutB

Perform a comprehensive layout audit on the current page to detect horizontal overflow, text clipping, unconstrained media, rigid fixed widths, and overlapping elements with severity ratings (Critical, High, Medium, Low).

inspect_consoleA

Capture and inspect browser console output: JavaScript errors, warnings, uncaught exceptions, and console messages.

inspect_networkA

Capture and inspect network activity: failed requests, HTTP 4xx/5xx responses, resource types, and failure reasons (avoids capturing sensitive auth tokens or cookies).

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

Disambiguation2/5

Six tools (audit_layout, detect_overflow, test_responsiveness, inspect_breakpoints, inspect_element_responsiveness, compare_viewports) all perform responsive/overflow analysis with heavily overlapping findings, and inspect_page vs inspect_page_structure vs inspect_element/inspect_styles also overlap on returning DOM and style data. Descriptions hint at differences in scope and output format, but an agent asking 'does this page overflow?' has no obvious single correct choice.

Naming Consistency5/5

All 17 names are snake_case and verb-first (navigate_, inspect_, open_, audit_, test_, detect_, compare_, capture_), which maps cleanly to the resource/action being performed. No camelCase or bare-noun outliers.

Tool Count3/5

17 tools is at the heavy end for a browser-inspection server, and the count is inflated by overlapping responsive/overflow tools that could be consolidated into two or three with parameters. The core inspection set (open, navigate, inspect DOM/styles/console/network, screenshot) is justified, but the audit family is redundant.

Completeness4/5

For a read-only inspection-and-audit server the lifecycle is well covered: open/navigate/reload, DOM and style introspection, console and network capture, responsive testing across breakpoints, and screenshots. The main gap is any form of page interaction (click, type, scroll) or session teardown, which limits verification of dynamic states but is arguably outside the stated audit purpose.

Maintenance

ActivityMaintained
ResponsivenessOutdated data