Lancelot
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANCEDB_PATH | Yes | The LanceDB database folder. Required for the tools to work. It must exist; Lancelot does not create it. | |
| LANCEDB_TABLE | No | Table used when a call names none. | documents |
| OPENAI_API_KEY | No | Enables vector search. When unset, the credential store is checked next. | |
| EMBEDDING_MODEL | No | The OpenAI model used to embed queries. | text-embedding-ada-002 |
| LANCELOT_LOG_LEVEL | No | One of error, warn, info, http, verbose, debug, silly. | info |
| LANCEDB_TEXT_COLUMN | No | Column holding the text. | text |
| EMBEDDING_DIMENSIONS | No | Reported by lancedb_status. It is not sent to OpenAI. | 1536 |
| LANCEDB_DEFAULT_LIMIT | No | Hits returned when a call sets no limit. | 20 |
| LANCEDB_VECTOR_COLUMN | No | Column holding the vectors. | vector |
| LANCEDB_CONTEXT_BUDGET | No | Characters of context lancedb_query returns when a call sets no contextBudget. | 8000 |
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 |
|---|---|
| lancedb_searchC | Search LanceDB for relevant documents using vector or text search |
| lancedb_queryC | RAG query with context retrieval from LanceDB |
| lancedb_statusC | Get LanceDB status and statistics |
| lancedb_versionB | Show Lancelot version information |
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 4 tools
lancedb_search and lancedb_query have overlapping retrieval purposes; an agent could easily pick the wrong one without careful reading. The descriptions distinguish them somewhat (raw search vs RAG context retrieval), but the boundary is not crisp. Status and version are clearly distinct.
All four tools use a consistent lancedb_<verb/noun> prefix pattern. Names are readable and predictable throughout.
Four tools is on the thin side but reasonable for a focused retrieval/status server. No obvious bloat, though the surface feels minimal.
The surface only covers search/query/status/version; there is no way to create or ingest documents, list tables, update, or delete data. For a LanceDB server, these are significant lifecycle gaps that would force agents to fail on write/admin tasks.