DeltaTask MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_task_by_idB | Get details for a specific task by ID. |
| search_tasksC | Search tasks by title, description, or tags. |
| create_taskC | Create a new task. |
| update_taskC | Update an existing task. |
| delete_taskC | Delete a task. |
| sync_tasksB | Sync tasks from Obsidian markdown into SQLite. |
| list_tasksB | List all tasks with optional tags, if you user asks for a tag, please provide it in the request. |
| get_statisticsB | Get task statistics including completion rates and urgency distribution. |
| create_subtasksC | Create multiple subtasks for a parent task with categories. |
| get_all_tagsB | Get all unique tag names used in tasks. |
| get_subtasksB | Get subtasks for a given parent task ID. |
| finish_taskB | Mark a task as completed. |
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 12 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, create_task and create_subtasks handle different operations, while list_tasks and search_tasks offer complementary but non-overlapping ways to retrieve tasks. The descriptions clearly differentiate each tool's function.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_task, delete_task, and get_subtasks. This predictability makes it easy for an agent to understand and select the appropriate tool without confusion.
With 12 tools, the server is well-scoped for task management, covering CRUD operations, subtasks, tags, statistics, and syncing. Each tool earns its place by addressing a specific need in the domain without being excessive or insufficient.
The tool surface provides complete CRUD and lifecycle coverage for task management, including creation, retrieval, updating, deletion, completion, subtasks, tags, search, statistics, and syncing. There are no obvious gaps that would hinder an agent's workflow.