Loading ToolBench

Reading the current corpus…

todoist-semantic-mcp-server MCP server · D · ToolBench

todoist-semantic-mcp-server

github.com/gwpl/todoist-semantic-mcp-server

A Model Context Protocol (MCP) server for integrating Claude with Todoist, allowing Claude to manage tasks, projects, and labels in a user's Todoist account.

<=2025-11-25STDIO13 tools

52/100

Definition Quality78

Protocol Readiness32

Supportability23

Spec posture

Inferred effective spec <=2025-11-25·current baseline 2026-07-28

Static source inference · medium confidence · detected: Logging

Deprecated protocol patterns detected

Summary

13 tools with complete schemas and descriptions. Naming is clear and verb-based (list-, create-, update-, delete-). Descriptions are detailed (100-300 chars) and explain use cases well. However, parameter descriptions lack actionable constraints (no enums for priority/color, no format specs for dates). Output schemas are not documented, LLMs cannot predict response structure. Error handling is absent from descriptions. Destructive tools (delete-task, delete-project, delete-label) lack confirmation/dry-run patterns. No tool annotations (readOnlyHint, destructiveHint) visible in code.

Tools (13)

complete-taskwriteauthsource verified70/100

Mark a task as complete in Todoist.

create-labelwriteauthsource verified82/100

Create a new label in Todoist. This tool allows you to create a new label with various properties, including: - Name - Color - Favorite status Usage examples: - "Create a new label called 'urgent'" - "Add a label 'research' with color blue" - "Create a label 'important' as a favorite"

create-projectwriteauthsource verified82/100

Create a new project in Todoist. This tool allows you to create a new project with various properties, including: - Name - Color - Parent project (for nested projects) - Favorite status Usage examples: - "Create a new project called 'Home Renovation'" - "Add a project 'Q2 Goals' with color red" - "Create a project 'Books' as a favorite"

create-taskwriteauthsource verified82/100

Create a new task in Todoist. This tool allows you to create a new task with various properties, including: - Task content (title) - Description - Project assignment - Due date - Priority - Labels Usage examples: - "Create a task 'Buy groceries' due tomorrow" - "Add a task 'Prepare presentation' to project 'Work' with priority 1" - "Create a task 'Call John' due on 2023-12-15 with label 'Personal'"

delete-labeldestructiveauthsource verified70/100

Delete a label from Todoist. This tool allows you to permanently delete a label. NOTE: This will remove the label from all tasks that use it. Usage examples: - "Delete label X" - "Remove the 'old' label"

Issues (5)

HIGHresponse-shaper ↗

Output schemas not documented. LLMs cannot predict response structure (fields, types, pagination). Forces agents to guess what data is returned.

list-taskscreate-tasklist-projectscreate-projectlist-labelscreate-label

HIGHconfirmation-request ↗

Destructive tools (delete-task, delete-project, delete-label) lack confirmation/dry-run pattern. No guard against accidental deletion by agents.

delete-taskdelete-projectdelete-label

HIGHconstrained-input ↗

Parameter constraints missing. 'priority' accepts 1-4 but no enum; 'color' accepts free-form strings (should be enum: berry_red, blue, green, etc.). LLMs will hallucinate invalid values.

create-taskupdate-taskcreate-projectupdate-projectcreate-labelupdate-label

Recommendations

Document output schemas for all tools. E.g., list-tasks returns {tasks: [{id, content, due_date, priority, labels, project_id}], total_count, has_more}. Include pagination fields (limit, offset, next_cursor).
Add enum constraints to color and priority parameters. Replace 'color (e.g., berry_red, blue, green)' with explicit enum: ['berry_red', 'blue', 'green', 'red', 'orange', 'yellow', 'lime_green', 'mint_green', 'teal', 'cyan', 'light_blue', 'purple', 'pink', 'gray'].
Implement confirmation pattern for destructive tools. Add optional 'confirm' boolean parameter (default false). When false, return {status: 'confirmation_required', message: 'This will permanently delete...', confirm_token: '...'}. Require confirm=true + token to execute.
Expand descriptions for simple tools (complete-task, delete-task, etc.) to 80-150 chars. Include: what happens, when to use, and recovery guidance. E.g., 'Mark a task as complete in Todoist. Once completed, the task moves to the Completed section and cannot be edited. Use list-tasks with completed=true to view completed tasks.'
Add tool annotations to server.py tool registration. Mark list-* and complete-task as readOnlyHint=true (or false for write ops); mark delete-* as destructiveHint=true; mark create-* as idempotentHint=false (or true if using idempotency keys).

Spec posture evidence

Inferred effective spec: <=2025-11-25.

Relies on Logging (deprecated) - log to stderr or use OpenTelemetry

Score history

Overall score trend

First recorded score · v2 rubric

52/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	D	52	<=2025-11-25	v2