A task management server based on Model Context Protocol (MCP), providing structured task management for AI agents
Server has 9 tools with explicit schemas and descriptions. Naming follows verb_noun convention (new_task, update_task, manage_*). Descriptions are present and moderately detailed (100-250 chars typical), explaining WHAT and WHEN. However, parameter descriptions are generic ('Task ID (supports short prefix matching)' repeated across tools), and output schemas are not documented, responses are serialized Task objects without field-level guidance. Error handling converts StoreError to text results but lacks recovery guidance. No tool annotations (readOnlyHint, destructiveHint). Composition is reasonable: separate tools for CRUD, checklist, notes, resources, projects. Missing: pagination for list_tasks, per-item error reporting for batch operations, and natural-language identifier support (only UUIDs with prefix matching).
Delete a task and all its associated data (checklist items, notes, resources). This action is irreversible. The task_id parameter supports short ID prefix matching (minimum 4 characters of the UUID).
Retrieve a single task by ID. The task_id parameter supports short ID prefix matching (minimum 4 characters of the UUID). Returns the complete task object including all checklist items, notes, resources, and metadata.
List all tasks, optionally filtered by project. Returns a list of task summaries with basic information. Use project_id to filter tasks by project association.
Perform operations on checklist items. NOTE: All checklist item indices are 0-based (the first item has index 0). Select the action based on what you need: - "add": Append a new item. Provide task (short name) and detailed_description. context_and_plan is optional. - "update": Modify an existing item's fields. Provide index (0-based). Only specified fields are changed. Set done=true to mark completed, done=false to revert. Pass context_and_plan to update or clear the plan field.
Perform operations on task notes. Select the action based on what you need: - "add": Append a new note. Provide content. - "update": Modify an existing note. Provide index (0-based) and new content. - "remove": Delete a note. Provide index (0-based).
Output schemas not documented. Tools return serialized Task/Project objects without field-level descriptions. LLMs cannot infer which fields are present, their types, or how to chain results to downstream tools.
list_tasks lacks pagination (limit, offset, total_count). No guidance on result limits. Large task lists will blow context windows and degrade LLM reasoning.
Error handling returns plain text error messages without recovery guidance. 'Task not found' does not tell the LLM to call list_tasks() or search by prefix. Errors should be actionable.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | <=2025-11-25 | v2 |
Perform operations on projects. Select the action based on what you need: - "create": Create a new project. Provide name and optional description. - "list": List all projects. - "get": Get a single project by ID. Provide project_id. - "update": Update project name and/or description. Provide project_id and fields to update. - "delete": Delete a project. Provide project_id. Deleting a project removes the project association from all tasks but does not delete the tasks themselves.
Perform operations on task resources. Select the action based on what you need: - "add": Append a new resource. Provide name, url, and optional description. - "update": Modify an existing resource. Provide index (0-based) and fields to update. - "remove": Delete a resource. Provide index (0-based).
Create a new task with a description, optional checklist items, notes, resources, and metadata. Usage: For multi-step tasks, provide initial_checklist to plan sub-tasks upfront. Use context_for_all_tasks to share background information across all sub-tasks (e.g., tech stack, constraints). Tag is sequence of strings. project_id is required to associate the task with a project. Use manage_project (action: "list") to find available project IDs.
Update task-level fields: description, context, priority, tags, estimated completion time, and/or project association. Only specified fields are modified. Usage: This is the single entry point for all task-level updates. Set project_id to a project UUID to assign the task to that project, or set project_id to null to remove the task from its current project. At least one field must be specified. The task_id parameter supports short ID prefix matching (minimum 4 characters of the UUID).
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). delete_task and manage_project (delete action) are destructive but unmarked. LLMs cannot distinguish safe from risky operations.
Parameter descriptions are repetitive and generic ('Task ID (supports short prefix matching)' appears 6+ times). Descriptions should explain WHEN to use each tool and dependencies (e.g., 'Call manage_project (action: list) first to find project_id').