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.

Quota-aware router over free web-search/scrape providers. Tools: search, read, deep_research, browser, create_image, usage. Pass provider to restrict routing to a specific backend (quota and retry limits still apply); otherwise providers are tried in the user's priority order with automatic failover.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
browserB

Load a URL in a headless browser (hyperbrowser, browserless, steel) and return the page as markdown.

create_imageA

Generate or edit an image via a logged-in web session. For a new image pass prompt; in local stdio mode, edit an existing image by passing its absolute path in file and describing the changes. To continue editing a ChatGPT-generated image in the same chat, pass the returned session back. Local stdio and the local hosted bridge save the result and return its path; use path to choose the local destination. Direct hosted HTTP returns inline artifacts without writing server paths.

deep_researchA

Deep research over multiple sources (parallel, exa, tavily, tinyfish, linkup, you, gemini_web, grok_web, chatgpt_web); may take minutes. gemini_web and chatgpt_web first return a research PLAN plus a session: pass that session with query "start" to run it, or with a revised request to replace the plan. gemini returns the finished report in the same call; chatgpt runs ~5-30 min after "start" — call again with the returned session to fetch the report (model is ignored there). Knobs: topic, recency, domains, depth ("deep" is slower/pricier). Provider-specific extras → call usage(provider=…).

readA

Read a URL and return its main content as clean markdown; auto-escalates to a headless browser when the plain read comes back empty. Provider-specific extras via mode (crawl, structured extract, screenshot…) → call usage(provider=…) for exact params & example calls.

searchA

Web search across quota-aware providers. API providers return ranked title/url/snippet results; web providers (gemini_web, grok_web, chatgpt_web) return a synthesized answer with sources and a session token for follow-up turns. For chatgpt_web this is a full chat turn with web search on by default — mode="chat" answers from the model alone. In local stdio mode, attach files with file to ask about them. Niche knobs: topic, recency, domains. Provider-specific extras (scholar/patents/places, structured extract…) → call usage(provider=…) for exact params & example calls.

usageA

Show remaining free quota per account and provider for the current period, plus each account's assigned proxy. For logged-in web sessions (grok/gemini/chatgpt) also includes live per-tier limits and the selectable model/mode catalog with thinking levels — a locked mode (e.g. grok Expert/Heavy on a lapsed sub) reads 0/0. Pass provider for that backend's full capability sheet — its niches, escape-hatch mode values, and ready-to-copy example calls.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation4/5

Most tools target clearly different actions (search, deep_research, create_image, usage), but browser and read overlap heavily since both load a URL and return markdown. The read description's note that it auto-escalates to browser helps, but an agent could still reasonably pick either for a simple fetch.

Naming Consistency3/5

All names are lowercase snake_case and readable, but conventions are mixed: bare verbs (read, search), bare nouns (browser, usage), a verb_noun (create_image), and a compound (deep_research). No single predictable pattern guides naming.

Tool Count5/5

Six tools is well within a healthy range and each earns its place: fetching, searching, deep research, image generation, and quota inspection. No obvious filler or missing companion tool.

Completeness4/5

The surface covers the core domain well: URL fetch via read/browser, search, multi-source research, image generation/editing, and quota introspection. Minor gaps include no explicit batch/multi-URL crawl tool (only available via provider-specific modes) and no dedicated session or result management beyond opaque tokens.

Maintenance

ActivityActive
ResponsivenessNo recent community issues