Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OLLAMA_HOSTNoOllama host URL.http://localhost:11434
GEMINI_MODELNoGemini model to use when `LOCAL_EYES_BACKEND=gemini`.gemma-4-31b-it
OLLAMA_MODELNoAny Ollama vision model.gemma4:e4b
GEMINI_API_KEYNoRequired for the `gemini` backend.
LOCAL_EYES_ROOTNoIf set, local paths must be inside this folder.
LOCAL_EYES_CACHENoSet to `1` to enable the replay cache (same as `--cache`).off
LOCAL_EYES_BACKENDNoBackend to use: `ollama` or `gemini`.ollama
LOCAL_EYES_MAX_SIDENoImages are downscaled to this maximum side length before sending.1600
LOCAL_EYES_CACHE_DIRNoDirectory used for cached validated responses../cache
LOCAL_EYES_ALLOW_PRIVATE_URLSNoURLs to localhost/private networks are refused by default.off

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
describe_imageB

Describe an image, or answer a question about it. path_or_url: absolute local path or http(s) URL.

extract_textB

OCR: return all visible text verbatim, plus any error/warning messages shown (great for UI screenshots).

read_uiB

Read a UI screenshot: structured elements (type, label, value, state), visible errors, and layout issues.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation4/5

The three tools carve out reasonably distinct niches: free-form description/Q&A, verbatim OCR, and structured UI element extraction. The main friction is that extract_text is explicitly pitched at UI screenshots, overlapping with read_ui, and describe_image's open-ended 'answer a question' scope can subsume either of the others.

Naming Consistency5/5

All three names follow a clean verb_noun snake_case pattern (describe_image, extract_text, read_ui), with the verb matching the action and the noun matching the input/artifact.

Tool Count4/5

Three tools is on the lean side but well-matched to a narrow image-inspection domain, with each tool earning its place. It sits just above the 'thin' threshold and leaves little room for edge cases like metadata or region-specific reads.

Completeness4/5

The surface covers the core jobs of local image understanding: general description, text extraction, and structured UI parsing, with clear input handling via path or URL. Minor gaps exist for basic image metadata (dimensions/format) or comparing/reading a specific region, but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues