Skip to main content
Glama
enesjakozh
Johnxjp

Todoist Python MCP Server

by Johnxjp
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

complete_task

Mark a Todoist task as completed by providing its task ID to update task status and manage your to-do list.

Instructions

Mark a task as done

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes

Implementation Reference

  • todoist_server.py:236-246 (handler)
    The complete_task tool handler, decorated with @mcp.tool(). It marks the specified Todoist task as done using the todoist_api.close_task method, handling errors appropriately.
    @mcp.tool()
def complete_task(task_id: str) -> str:
    """Mark a task as done"""
    try:
        task_id = task_id.strip('"')
        is_success = todoist_api.close_task(task_id=task_id)
        if not is_success:
            raise Exception
        return "Task closed successfully"
    except Exception as e:
        raise Exception(f"Couldn't close task {str(e)}")

Tool Definition Quality

C2.6/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. 'Mark a task as done' implies a mutation (changing task status), but it doesn't specify permissions required, whether the change is reversible, side effects (e.g., notifications), or error handling. It lacks details on what 'done' entails operationally, leaving behavioral traits unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero waste. It's front-loaded and appropriately sized for a simple tool, avoiding unnecessary elaboration while stating the core action clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's mutation nature, lack of annotations, no output schema, and low schema coverage, the description is incomplete. It doesn't cover behavioral aspects like side effects, return values, or error conditions, leaving significant gaps for an agent to operate effectively in context with siblings like 'update_task'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. The description mentions 'task' but doesn't explain the 'task_id' parameter's semantics, such as format, source, or validation rules. It adds minimal meaning beyond the schema, failing to address the coverage gap adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Mark a task as done' clearly states the action (marking) and resource (task), but it's somewhat vague about what 'done' means (completed, archived, etc.). It distinguishes from siblings like 'create_task' and 'delete_task' by focusing on status change rather than creation or removal, but doesn't explicitly differentiate from 'update_task' which might also handle status updates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., task must exist), when not to use it (e.g., for partial completion), or direct alternatives like 'update_task' for more complex modifications. The agent must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Johnxjp/todoist-mcp-python'

If you have feedback or need assistance with the MCP directory API, please join our Discord server