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

Tools

Functions exposed to the LLM to take actions

NameDescription
auth_fetchA

Read a login-protected page using a local browser and human-approved capture. Use for authenticated pages or when normal web reading returns a login screen or empty content. Tell the user to sign in and click Capture page before calling. Returns a loaded-DOM snapshot, source URL, time, links, media and completeness warnings. Prefer format=text for reading; html preserves markup. Canvas, frame contents and unloaded content are not extracted. This call waits for the user.

download_mediaA

Download only attachments needed for the user's task using saved browser cookies. Returns local paths, sizes, and per-file errors. Check downloaded before reporting success. Cookies may not cover sites that require JavaScript-generated authorization headers. Use include_preview to return small PNG/JPEG/WebP images directly to the AI; larger files need a local file viewer. Run after auth_fetch finishes.

list_pagesA

Inspect open browser tabs without navigating. Returns URLs and titles; it does not capture page content.

close_browserA

Close the browser when the user asks to cancel. An active capture will fail; saved login sessions are retained. Do not call during capture unless cancellation is intended.

Prompts

Interactive templates invoked by user choice

NameDescription
read_authenticated_pageRead and summarize a page through human-approved browser capture.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct browser action: list_pages inspects tabs, auth_fetch captures content, download_media fetches attachments, and close_browser tears down. Boundaries are clean and the descriptions reinforce the sequencing (auth_fetch before download_media, close only when cancelling).

Naming Consistency4/5

close_browser, download_media, and list_pages follow a clear verb_noun snake_case pattern. auth_fetch deviates slightly (reads as noun/qualifier + verb) but remains readable and consistent in casing.

Tool Count5/5

Four tools is well-scoped for a narrow authenticated-fetching purpose, with each tool earning its place. No redundant or filler tools, nothing obviously missing at this count.

Completeness4/5

The full lifecycle is covered: inspect tabs, capture content, download media, and close the browser. A dedicated navigation/URL-open tool appears absent, but list_pages plus the user-driven capture flow largely compensates.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive