lance-kb
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANCE_KB_DIR | No | Where the LanceDB table lives. | kb-data |
| LANCE_KB_MODEL | No | Any sentence-transformers model. `hash` uses a tiny bag-of-words embedder with no download, meant for tests. | BAAI/bge-small-en-v1.5 |
| LANCE_KB_DEVICE | No | `cpu`, `cuda` or `mps`. | auto |
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchB | Search notes and document chunks. mode is "hybrid" (vector + keyword, merged with RRF), "vector" or "text". Filter by project, kind ("note" or "chunk") or tag. Pass version to search the knowledge base as it was at that version (see list_versions). |
| getB | Fetch one note or chunk by id, with its full text and metadata. |
| add_noteC | Save a note (a decision, a finding, a how-to). Returns its id. |
| update_noteB | Change a note's title, text, project or tags. It is re-embedded automatically. |
| deleteB | Delete a note or chunk. It stays recoverable through restore_version. |
| ingest_folderA | Index the Markdown, text and reStructuredText files under path, chunked by heading with file and line provenance. Unchanged files are skipped; changed files are re-chunked. |
| list_versionsA | List the knowledge base's versions (every write creates one). |
| restore_versionA | Make an older version current again (a new version is written; history is kept). |
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 8 tools
Each tool has a distinct action: get by id, search by query, add/update/delete notes, ingest folders, and manage versions. Although get/search/delete all operate on notes or chunks, their purposes and inputs are clearly separable.
All names use snake_case, but the convention is mixed: add_note, update_note, ingest_folder, list_versions and restore_version are verb_noun, while get, search and delete are bare verbs. Still readable, but not a single predictable pattern.
Eight tools is well-scoped for a knowledge-base server: CRUD for notes, search, folder ingestion, and version list/restore. Each tool earns its place without obvious redundancy.
The surface covers note creation, retrieval, update, deletion, search, ingestion, and version history/restore, so core lifecycle workflows are complete. Minor gaps exist around browsing/listing notes, projects or tags directly, but search filters largely compensate.