mcp-lance-db
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_memoryC | Add a new memory to the vector database Args: content: Content of the memory |
| search_memoriesC | Search memories using semantic similarity Args: query: The search query limit: Maximum number of results to return |
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 2 tools
The two tools have completely distinct purposes: one adds a memory, the other searches. There is no overlap or ambiguity.
Both tools follow the consistent verb_noun snake_case pattern: add_memory and search_memories. No deviations.
With only 2 tools, the server covers basic add and search functionality, but feels thin. It is borderline appropriate given the minimal scope.
The domain of a memory store expects operations like delete or update, which are missing. The tool set covers only creation and retrieval, leaving significant gaps.