Local Knowledge Desk
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KNOWLEDGE_DESK_NOTES_DIR | No | Optional path to a custom notes directory. Defaults to `data/notes` relative to the server's working directory. | data/notes |
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": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_noteA | Create a new local Markdown note without overwriting an existing note. |
| list_notesB | List local note IDs and titles. |
| read_noteB | Read one local Markdown note by ID. |
| search_notesB | Search local note titles and bodies. |
| workspace_summaryA | Summarize the number and titles of local notes. |
| delete_noteA | Delete a local note after explicit confirmation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| daily_review | Review local notes to identify the day's most important priorities. |
| research_digest | Research a topic across local notes and produce a sourced digest. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a distinct purpose: create, delete, list, read, search, and summarize. No overlaps or ambiguities exist.
All tool names use imperative verbs and snake_case, with 'workspace_summary' being a noun-based outlier but still following the same formatting.
Six tools cover the essential CRUD operations plus search and summary without being excessive.
The set lacks an 'update_note' tool, which is a notable gap for full lifecycle management. Create and delete are present, but editing requires deletion and recreation.