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.

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
lexicon_searchA

Search the Lexicon: curated project notes, in-place repo documentation, and archived Claude Code / Codex / ChatGPT session transcripts. Hybrid lexical (FTS5) plus semantic (local embeddings) search. Use before re-solving a nontrivial problem to find prior work, past decisions, and approaches that already failed.

Reading the results: score is ordinal and only orders one result set against another in the same query -- it says nothing about whether the Lexicon actually covers the topic. confidence does: it is absolute, runs 0.15-1.00, and is comparable across queries. At or above 0.80 the corpus genuinely covers the point; between 0.60 and 0.80 treat the result as partial or tangential and verify before relying on it. If most results sit below that, the honest answer is that the Lexicon does not cover this -- say so instead of stretching a weak hit. matched_by shows which leg found it: fts is an exact lexical match, vector a semantic one, and both together is the strongest signal.

lexicon_readA

Read an indexed document, or one chunk of it with surrounding context. Use after lexicon_search to expand a promising result: pass that result's path and chunk_ord.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

lexicon_search and lexicon_read have clearly distinct roles: one finds relevant results across the corpus, the other expands a specific indexed document. There is no overlap or ambiguity between the two.

Naming Consistency5/5

Both tools follow the same lexicon_ prefix with an action verb in snake_case: lexicon_search and lexicon_read. This creates a clean, predictable naming pattern.

Tool Count4/5

Two tools is minimal, but for a read-only local knowledge retrieval server, search-and-read is the core interaction loop. It is slightly thin compared to typical server scopes, but each tool earns its place.

Completeness4/5

The search-to-read workflow is complete for consuming the Lexicon, including clear guidance on interpreting result confidence. Missing are corpus-level operations like listing indexed documents or ingesting new content, but those appear outside this server's stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues