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

Tools

Functions exposed to the LLM to take actions

NameDescription
wiki_queryA

Start here for questions about the user's past work ('what did I decide about X', 'how did I fix Y'), in any language: session pages keep the user's original request. Ranks wiki/ pages by keyword matches, rare words weighted higher (no LLM, no embeddings); service pages are skipped and project overview pages rank below sessions. Sessions that name the same tool or topic as two or more top hits rank too, marked 'via '. If no wiki page matches, it falls back to raw transcripts (see include_raw). Returns up to max_pages paths with a ~400-character snippet each, plus the start of wiki/overview.md; with no match, the start of wiki/index.md. Read-only. Open a full page with wiki_read_page; use wiki_search for exact wording.

wiki_searchA

Find exact text: case-insensitive substring match, line by line, over wiki/ pages, plus raw session transcripts in raw/sessions/ when include_raw=true. Returns JSON {term, matches: [{path, line, text}], truncated, scan_incomplete, files_scanned, files_total, skipped_oversize_files}; stops at 200 matches (truncated), skips files over 4 MiB and reads at most 256 MiB per call (scan_incomplete). Read-only. Use wiki_query instead for ranked, question-style lookup; open a hit with wiki_read_page.

wiki_list_sourcesA

List raw session transcripts in raw/sessions/ (one markdown file per agent session), sorted by path, oldest first. Returns a JSON array of {path, project, date, filename, size_bytes}; project and date come from each file's frontmatter. Read-only. Use it to see which sessions exist for a project, then open one with wiki_read_page.

wiki_read_pageA

Return the full text of one file, unmodified and not truncated. path is relative to the sessionwiki folder and must be under wiki/, raw/, docs/, examples/ or site/ (or README.md, CHANGELOG.md, CONTRIBUTING.md, LICENSE). Returns an error if the path is outside that set, escapes the folder, or does not exist. Read-only. Get paths from wiki_query, wiki_search or wiki_list_sources.

wiki_lintA

Check the link structure of wiki/: find orphan pages (no inbound [[wikilinks]]; index, overview and log are exempt) and broken [[wikilinks]] that point to no page. Returns JSON {total_pages, orphan_count, orphans, broken_link_count, broken_links}, listing at most 50 of each. Read-only: it reports and changes nothing. Use it after wiki_sync or before publishing; use wiki_lifecycle or wiki_confidence to review page quality.

wiki_syncA

Convert new agent sessions (Claude Code, Codex, Cursor, ZCode, OpenCode, ...) from their local session stores into markdown under raw/sessions/. Dry run by default: it only reports what would change. It writes only with dry_run=false and confirm=true; ask the user before that. A real run adds new files and never overwrites existing ones, so repeating it is safe; it may also rebuild site/. Returns the converter's output (last 256 KB) and fails after 120 s. Use it when wiki_list_sources lacks recent sessions.

wiki_exportA

Return one generated export file from site/ as text, to load the whole wiki at once: 'llms-txt' (short llms.txt index), 'llms-full-txt' (all pages flattened), 'jsonld' (schema.org graph), 'sitemap' (sitemap.xml), 'rss' (feed of recent pages), 'manifest' (build manifest.json), or 'list' (JSON list of the export files that exist, with sizes). Output is cut at 200 KB. Read-only. Fails if the file is missing; run sessionwiki build first. For specific facts wiki_query is cheaper.

wiki_confidenceA

List wiki pages whose frontmatter confidence (0.0-1.0) is between min_confidence and max_confidence; pages without a confidence value are left out. Returns plain text: the match count, then up to 50 lines of 'score path - title', lowest score first. Read-only. Use max_confidence=0.5 to find weak pages to recheck; use wiki_dashboard for the overall distribution.

wiki_lifecycleA

List wiki pages whose frontmatter lifecycle equals state (draft, reviewed, verified, stale or archived). Returns plain text: the match count, then up to 50 lines of 'last_updated path - title', newest first. Read-only. Use 'stale' or 'draft' to find pages to update; use wiki_dashboard to see how many pages are in each state.

wiki_dashboardA

Overview of the whole wiki in one call: total page count, pages per type (source, entity, concept, ...), pages per lifecycle state, and how many pages have high (>=0.8), medium, low (<0.5) or no confidence. Returns plain-text Markdown. Read-only, no parameters. Call it first to see the wiki's size and health, then use wiki_lifecycle or wiki_confidence for the page lists.

wiki_entity_searchA

Find entity pages (people, orgs, tools, libraries, APIs, projects, concepts): wiki pages with type: entity. name matches a case-insensitive substring of the title or path; entity_type matches exactly; when both are given both must match; with neither, every entity is listed. Returns plain text: the count, then up to 50 lines of '[type] path - title', sorted by title. Read-only. Use wiki_query for free-text questions and wiki_category_browse for tags.

wiki_category_browseA

Browse the wiki by tag (the 'tags' frontmatter field; 'category' here means tag). Without tag: lists tags used by at least min_count pages, most used first, up to 100. With tag: lists up to 50 pages with that tag as 'path - title' (min_count is ignored). Returns plain text. Read-only. Use wiki_entity_search for named things and wiki_query for free-text questions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 12 tools

Disambiguation4/5

The four search-ish tools (wiki_query, wiki_search, wiki_entity_search, wiki_category_browse) overlap in intent, but each description explicitly states its niche and points to the others ('use wiki_query for free-text questions', 'use wiki_search for exact wording'). The three listing tools (wiki_dashboard, wiki_lifecycle, wiki_confidence) are similarly delineated: dashboard is the aggregate, the other two filter on a single frontmatter field. Only minor residual ambiguity remains for an agent choosing between ranked query and tag/entity browsing.

Naming Consistency4/5

All 12 tools share the wiki_ prefix, which makes the set immediately recognizable. Most follow verb_noun (wiki_read_page, wiki_list_sources, wiki_entity_search, wiki_category_browse, wiki_search, wiki_query), but wiki_confidence, wiki_lifecycle and wiki_dashboard are noun-only names and wiki_lint has no object, a small deviation from the pattern.

Tool Count4/5

12 tools is well within a reasonable scope for a wiki/knowledge-base server and each maps to a real operation (retrieval, listing, health checks, sync, export). There is mild redundancy in having three separate page-listing tools (lifecycle, confidence, dashboard) that could conceivably be one parameterized tool, but nothing feels padded.

Completeness3/5

The read/retrieve/inspect side is thorough (ranked query, exact search, read, lint, dashboard, filters, export), but the surface is essentially read-only: there is no tool to create, edit, or delete a wiki page, and no way to add tags or frontmatter, so an agent that needs to correct or author content hits a dead end. Sync only ingests raw session files, which partially compensates but does not cover page authoring.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues