lazymark
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesB | Lists the Lazymark notes with their path, title, tags and number of tasks. |
| read_noteB | Reads the Markdown content of a note in the notes folder. |
| create_noteB | Creates a new note (from the template, or with just its title if empty is true) and returns its path. |
| search_notesA | Searches text in all the notes (case-insensitive). Returns the note, line and context of each match, ordered by note and line. |
| list_tasksB | Lists the tasks with their id, text, board column and whether they are done. |
| move_taskA | Moves a task to another column of the Kanban board. It only rewrites the task's line; if the note changed on disk in the meantime, it writes nothing and returns an error. |
| set_task_dateA | Sets or removes the start date or the due date of a task, in an Obsidian Tasks format (the configured date format). It only rewrites the task's line. The completion date is handled by moving the task to the done column. |
| toggle_taskA | Marks a task as done (moves it to the done column) or, if it already was, returns it to the first column. |
| get_kanbanA | Returns the Kanban board: the configured columns, in order, each with its cards. |
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 9 tools
Most tools are clearly distinct by resource and action, especially note operations. However, list_tasks and get_kanban both expose task/board information, and toggle_task overlaps somewhat with move_task, though descriptions clarify intended use.
All tool names use snake_case and a consistent verb_noun pattern. The slight variation among verbs like get, read, and list is semantically appropriate and does not create confusion.
Nine tools is well-scoped for a note and Kanban helper. Each tool corresponds to a clear operation without obvious bloat or missing coverage in count.
The server covers reading, searching, and listing notes plus several task manipulations. However, it lacks note update/delete or general editing, and has no explicit task creation, deletion, or text update, creating notable dead ends for a note-management domain.