Skip to main content
Glama
guifelix

MCP Todo.txt Integration

complete-task

Mark a task as completed by its ID to update your Todo.txt file and track progress.

Instructions

Mark a task as completed by its 1-based ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskIdYes

Implementation Reference

  • Handler that loads the task list, converts 1-based ID to index, marks the task as completed with today's date if found, saves the list, or returns error if not found.
    async ({ taskId }) => {
        const tasks = await loadTasks();
        const idx = getTaskIndex(taskId, tasks);
        if (idx === null) {
            return {
                content: [
                    { type: "text", text: "Task not found." },
                ],
                isError: true,
            };
        }
        tasks[idx].setCompleted(new Date().toISOString().split("T")[0]);
        await saveTasks(tasks);
        return {
            content: [
                { type: "text", text: "Task marked as completed." },
            ],
        };
    }
  • Input schema defining taskId as a required number (1-based index).
    { taskId: z.number() },
  • src/tools.ts:59-82 (registration)
    Registers the complete-task tool on the MCP server with name, description, input schema, and handler function.
    server.tool(
        "complete-task",
        "Mark a task as completed by its 1-based ID.",
        { taskId: z.number() },
        async ({ taskId }) => {
            const tasks = await loadTasks();
            const idx = getTaskIndex(taskId, tasks);
            if (idx === null) {
                return {
                    content: [
                        { type: "text", text: "Task not found." },
                    ],
                    isError: true,
                };
            }
            tasks[idx].setCompleted(new Date().toISOString().split("T")[0]);
            await saveTasks(tasks);
            return {
                content: [
                    { type: "text", text: "Task marked as completed." },
                ],
            };
        }
    );
  • Helper function to convert 1-based task ID to 0-based array index, returns null if invalid.
    function getTaskIndex(taskId: number, tasks: Item[]): number | null {
        const idx = taskId - 1;
        if (idx < 0 || idx >= tasks.length) return null;
        return idx;
    }
  • Helper function to persist the tasks list to the TODO file.
    async function saveTasks(tasks: Item[]) {
        const content = tasks.map((task) => task.toString()).join("\n");
        await fs.writeFile(TODO_FILE_PATH, content, "utf-8");
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Mark a task as completed') but doesn't clarify if this is a mutation, what permissions are required, if it's reversible, or what happens on success/failure. For a tool that likely modifies state, this lack of detail is a significant gap.

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 that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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 complexity of a mutation tool with no annotations, no output schema, and minimal parameter details, the description is incomplete. It doesn't address behavioral aspects like side effects, error handling, or return values, leaving the agent with insufficient information for reliable invocation.

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

Parameters3/5

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

The description adds minimal semantics by specifying '1-based ID' for the 'taskId' parameter, which clarifies the indexing convention. However, with 0% schema description coverage and only one parameter, this provides some value but doesn't fully compensate for the lack of schema details, such as valid ID ranges or format constraints.

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

Purpose4/5

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

The description clearly states the action ('Mark a task as completed') and identifies the resource ('task'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'update-task' or 'delete-task' that might also operate on tasks by ID, leaving some room for confusion about why to choose this specific tool.

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?

The description provides no guidance on when to use this tool versus alternatives like 'update-task' (which might also mark tasks as completed) or other sibling tools. It mentions the parameter ('1-based ID') but doesn't explain prerequisites, such as needing an existing task ID, or when not to use it, making it minimally helpful for selection.

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/guifelix/mcp-server-todotxt'

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