Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FRD_BEARER_TOKENNoA strong, random secret used for bearer authentication; needed when running the server in HTTP mode (python server.py --transport http --port 8765). Set it using your OS secure environment settings.

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
read_linesB

Read at most 150 numbered lines of a scoped text file

search_textB

Search bounded project files locally and return concise line previews

list_job_recipesC

List deterministic workflows that make zero model calls

run_jobB

Execute a locally approved, deterministic workspace workflow; requires allow_jobs

job_historyC

List receipts for recent local deterministic jobs

desktop_statusB

Return desktop hostname, roots, and enabled capabilities

list_directoryA

List up to 200 entries in a permitted folder

read_text_fileA

Read a UTF-8 file within configured size limits

write_text_fileA

Write a UTF-8 file; disabled by default; no overwrite without explicit flag

run_commandB

Run only an exact allowlisted shell-free command; disabled by default

capture_screenA

Capture primary desktop as PNG; requires explicit opt-in

gui_clickB

Click primary desktop screen coordinates; requires explicit opt-in

gui_typeA

Type short text into current focused GUI element, requires explicit local GUI opt-in

gui_hotkeyB

Press an allowlisted keyboard shortcut, requires explicit GUI opt-in

browser_navigateA

Open allowlisted HTTPS URL in persistent headless browser

browser_snapshotA

Read the visible browser page text

browser_clickB

Click browser element by CSS selector; requires gui+browser capabilities

browser_fillB

Fill a non-password browser form field by CSS selector; requires browser+GUI opt-in

browser_screenshotB

Capture the current browser viewport as an image

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 19 tools

Disambiguation4/5

Most tools target clearly distinct resources or capability areas: jobs, filesystem, command execution, GUI, and browser. The main possible confusion is read_text_file versus read_lines, and to a lesser extent capture_screen versus browser_screenshot, but their descriptions make the contexts reasonably clear.

Naming Consistency4/5

Names are predominantly snake_case and action-oriented, with clear namespaced prefixes for GUI and browser operations. Minor deviations such as job_history and desktop_status use noun-first phrasing, but the overall convention remains readable and predictable.

Tool Count4/5

Nineteen tools is somewhat large, but the server covers several distinct capability families: jobs, filesystem, command execution, desktop GUI, and browser automation. Each tool appears to earn its place within those areas rather than being redundant bloat.

Completeness4/5

The surface covers core workflows for file reading/writing/listing/searching, command execution, job running/history, screen capture, GUI input, and browser interaction. Some gaps exist, such as no explicit file delete/move operations and limited browser navigation/history controls, but agents can generally work around them or the omissions are consistent with the safety-first design.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues