Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Semantic + lexical (hybrid) search over an indexed source. This is your PRIMARY search tool — use it FIRST for any question about the indexed code or docs. Omit source to search ALL sources at once (rankings fused via RRF, each hit tagged with its source); pass source to target one. Configured sources: . Best practices: use natural-language descriptions of what the code does, not exact identifiers (use grep for those). Good: 'method that handles player damage calculation'. Bad: 'CalculateDamage'. Args: query (natural language); source (optional name); top_k (default from config); file_glob, extensions, path_contains (optional filters). For broad/exploratory queries, or a large top_k, set outline=true to get signatures-only results (much cheaper to read): scan them, then pull just the one body you need with find_definition or its file:line. Use the default (full bodies) when you'll work with the code right away.

deep_searchA

Multi-query fallback search. ESCALATION TOOL — use only when search returned weak or empty results, or when the user explicitly asks for a more thorough search. Slower than search because it runs multiple retrievals. How it works: tries each query variant in order; stops at the first whose results pass the weakness threshold. If all fail, returns the strongest weak set with a warning. Omit source to run across ALL sources (RRF-fused); pass source to target one. Configured sources: . Best practices: provide 2-4 GENUINELY DIFFERENT phrasings (different angles, not paraphrases). Good: ['player health system', 'damage and healing logic', 'HP component lifecycle']. Bad: ['player health', 'health of the player'] (too similar). Args: queries (ordered list of variants); source (optional name); top_k; mode ('dense'|'sparse'|'hybrid', single-source only); file_glob, extensions, path_contains; min_score, min_results (threshold overrides); return_all_variants (per-variant diagnostics, single-source only).

list_sourcesA

List all configured sources with their type, location, chunk count, and drift status.

    Call this first when you don't know which sources are available.
    Pass a name from this list as the `source` argument of the other
    tools (`search`, `deep_search`, `graph_query`, `find_*`, ...).
    
update_source_indexA

Force a full rebuild of a specific source's index.

    Day-to-day the watcher keeps the index in sync automatically; you rarely need this.
    Use it after a complex merge, a bulk rename, or when drift detection flags a
    critical change (e.g. embedding model swap).

    Do NOT call this routinely — it is expensive and blocks until complete.
    Call `get_rag_status` first to check if a rebuild is actually needed.

    Args:
        source: Name of the source to rebuild. Use `list_sources` to discover names.
        force: If True, rebuild even when no new git commits are detected.
    
get_rag_statusA

Report state of the RAG index for one source or all sources.

    Use this to check if the index is up to date before deciding whether to
    call `update_source_index`. Also useful for debugging when search results
    seem stale or incomplete.

    Args:
        source: Specific source name to inspect. If None, returns the
            status of every configured source.
    
feedbackA

Report that you could not find what you needed. Call this BEFORE giving up after exhausting search / deep_search / graph_query. The report is appended to a LOCAL log file on this machine (rag_storage/_feedback/feedback.jsonl) — it is never uploaded anywhere — and helps the index owner tune sources, filters, and chunking. Args: trying_to_do (what you were trying to find or answer); tried (which tools/queries you already tried); stuck (where exactly you got blocked or what was missing).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
guideHow to use Lynx well: search phrasing, score interpretation, escalation ladder, structural queries.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lorenzo-cambiaghi/LynxMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server