agent-wiki
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WIKI_PATH | Yes | Path to the knowledge base directory (passed as --wiki-path) |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| raw_ingestA | Ingest raw source documents into the knowledge base. Select
|
| raw_versionsA | List all versions of a raw file, sorted by version number, with the latest version marked. Given a base filename (e.g. 'report.xlsx'), returns all matching versions (report.xlsx as v1, report_v2.xlsx, report_v3.xlsx, etc.) with metadata and a 'latest' field pointing to the newest file. |
| raw_listA | List all raw source documents with metadata (path, source URL, download time, hash, size). |
| raw_coverageA | Report which raw/ files are not yet referenced by any wiki page. Answers 'what should I compile next?' — returns uncovered files sorted by recency/size, plus overall coverage ratio. Matches frontmatter 'sources' and inline 'raw/...' body references. Parsed artifacts (raw/parsed/) are excluded. |
| raw_readA | Read a raw source document's content and metadata. Raw files are immutable — this is read-only. Text/SVG files return content as string; document files (PDF, DOCX, XLSX, PPTX) have text extracted automatically; other binary files (images, etc.) return metadata only. Pagination by format:
For large documents, paginate rather than reading all at once. |
| wiki_readA | Read one or more wiki pages. Single page: pass |
| wiki_writeA | Create or update a wiki page. Content should include YAML frontmatter (title, type, tags, sources) and Markdown body. Timestamps (created/updated) are auto-managed. Auto-routes root-level pages to matching topic subdirectories (via frontmatter |
| wiki_deleteB | Delete a wiki page. Cannot delete system pages (index.md, log.md, timeline.md). |
| wiki_listA | List all wiki pages, optionally filtered by entity type or tag. |
| wiki_searchA | Full-text keyword search across all wiki pages. Returns paths, scores, and snippets sorted by relevance. Uses BM25 by default; switches to hybrid BM25+vector re-ranking when |
| wiki_adminA | Wiki administration and maintenance. Select
|
| batchA | Execute multiple tool calls in a single request. Reduces tool-call count for LLM subscriptions that bill per-request (e.g. GitHub Copilot). Supports ANY combination of tools — e.g. read 5 wiki pages, write 3 pages, add 2 raw files, search, all in one call. Wiki index rebuild is automatically deduplicated (runs once at the end, not per-write). Each operation is independent — one failure does not abort the batch. Nested batch calls are not allowed. |
| knowledge_ingestA | Knowledge ingestion pipeline. Select
|
| code_parseA | Parse a source file from raw/ into structured code knowledge (AST, normalized model, summary). Currently supports COBOL (.cbl, .cob, .cpy). Persists artifacts under raw/parsed/cobol/. Optionally traces all references to a variable. |
| code_queryA | Query parsed code knowledge. Select
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose, with unique names and detailed descriptions that prevent confusion. Overlaps are minimal and well-explained, e.g., raw_ingest vs knowledge_ingest handle different stages of ingestion.
All tool names follow a consistent verb_noun pattern using snake_case, such as wiki_read, raw_ingest, code_query. This makes the API predictable and easy to navigate.
With 15 tools, the set is well-scoped for a comprehensive knowledge base server, covering ingestion, parsing, search, and administration without being excessive.
The tool surface covers the full lifecycle of a wiki/knowledge base: init, config, add/read/update/delete content, search, raw file management, code analysis, and maintenance tasks like linting and rebuilds. No obvious gaps.