Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DOCS_DIRNoDirectory where fetched markdown docs are saved./docs
CACHE_DIRNoDirectory for TTL cache (raw HTML + fetched markdown)./.cache/web-docs
USER_AGENTNoUser-Agent sent to upstream serversChrome-like UA
GITHUB_TOKENNoOptional GitHub token to lift rate limits
DISABLE_CACHENoDisable caching (useful for debugging)false
CACHE_TTL_HOURSNoCache time-to-live in hours168
HTTP_TIMEOUT_MSNoHTTP timeout per request in milliseconds20000
DEFAULT_SAVE_TO_DOCSNoDefault behavior for saving docs to docs/ foldertrue

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
web_searchA

Free web search via DuckDuckGo HTML (no API key, no per-query cost). Returns a list of {title, url, snippet}. Pass any URL to fetch_url for full content.

fetch_urlA

Fetch a single URL and return clean markdown. Handles HTML (via turndown+GFM), JSON (pretty-printed), and plain text. Cached locally. Optionally saves to docs/.md with YAML frontmatter (source URL, fetch date, content type).

lib_docsA

Fetch README/docs for a library by name. Tries npm → PyPI → crates.io → Go → GitHub automatically. Accepts react, numpy, serde, owner/repo, etc. Optionally saves to docs/libraries/.md.

search_docsA

Language & API documentation search. Biases DuckDuckGo results to official docs sites (MDN, docs.python.org, pkg.go.dev, doc.rust-lang.org, etc.). Set fetch_top=true to retrieve the full markdown of the top hit instead of just the result list. LOCAL-FIRST: searches your docs/ folder first; only falls back to the web if no local match.

list_docsA

Browse and search the local docs/ folder. Three modes: (1) no args = list all saved docs, (2) { query } = keyword search across docs/, (3) { path } = read the full body of a specific doc by relative path or slug. Use this BEFORE going to the web — your project may already have the docs you need.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 5 tools

Disambiguation4/5

Most tools have clear boundaries: fetch_url retrieves a specific URL, lib_docs fetches library docs by name, list_docs works with local files. The main overlap is between web_search and search_docs, both performing web searches, though search_docs is specifically biased to official documentation and is local-first, which distinguishes it. Descriptions are detailed enough to disambiguate in practice.

Naming Consistency4/5

All names use lowercase snake_case with an underscore, and most follow a verb_noun pattern (fetch_url, search_docs, list_docs). However, web_search is noun_verb order and lib_docs is noun_noun, which are minor deviations from the dominant pattern. Overall the style is consistent and readable.

Tool Count5/5

Five tools is a well-scoped size for a documentation reference server. Each tool serves a clear function: web search, URL fetching, library-specific fetching, docs search, and local docs browsing. This is within the ideal 3-15 range and there is no bloat.

Completeness5/5

The tool set covers the full workflow for web documentation research: searching the web, fetching pages, retrieving library docs, searching with docs bias, and managing local saved docs. The optional saving via fetch_url and lib_docs, plus list_docs for browsing, avoids dead ends. No critical gaps are evident for the documented purpose.

Maintenance

ActivitySlowing
ResponsivenessNo issues