Skip to main content
Glama
hevener10

MCP TODO Checklist Server

by hevener10

todo_complete

Mark checklist tasks as completed by specifying list and task titles to track progress and maintain organized workflows.

Instructions

Marca uma tarefa como concluída

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listTitleYesTítulo da lista
taskTitleYesTítulo da tarefa

Implementation Reference

  • Handler for the 'todo_complete' tool. Parses input arguments using completeSchema, locates the specified checklist and task by title, toggles the task's completion status via checklistService.toggleItemComplete, and returns a success message.
    case "todo_complete": {
      console.error('DEBUG - Processing todo_complete');
      const params = completeSchema.parse(args);
      const todoLists = await checklistService.getUserChecklists('current-user');
      const todoList = todoLists.find(l => l.title === params.listTitle);
      
      if (!todoList) {
        throw new Error(`Lista não encontrada: ${params.listTitle}`);
      }
    
      const task = todoList.items.find(t => t.title === params.taskTitle);
      if (!task) {
        throw new Error(`Tarefa não encontrada: ${params.taskTitle}`);
      }
    
      await checklistService.toggleItemComplete(todoList.id, task.id);
      return { content: [{ type: "text", text: `Tarefa "${params.taskTitle}" marcada como completa!` }] };
    }
  • Zod schema for validating input parameters of the todo_complete tool: listTitle and taskTitle.
    const completeSchema = z.object({
      listTitle: z.string(),
      taskTitle: z.string()
    });
  • src/index.ts:145-156 (registration)
    Registration of the 'todo_complete' tool in the ListTools response, including name, description, and input schema.
    {
      name: "todo_complete",
      description: "Marca uma tarefa como concluída",
      inputSchema: {
        type: "object",
        properties: {
          listTitle: { type: "string", description: "Título da lista" },
          taskTitle: { type: "string", description: "Título da tarefa" },
        },
        required: ["listTitle", "taskTitle"],
      },
    },
  • Helper method in ChecklistService that toggles the completion status of a checklist item by updating it with the inverted completed flag.
    async toggleItemComplete(checklistId: string, itemId: string): Promise<ChecklistItem> {
      const checklist = await this.getChecklist(checklistId);
      const item = checklist.items.find(item => item.id === itemId);
      
      if (!item) {
        throw new Error(`Item not found: ${itemId}`);
      }
    
      return this.updateItem(checklistId, itemId, { completed: !item.completed });
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool marks a task as completed, implying a mutation, but doesn't address permissions, side effects (e.g., if completion is reversible), error handling, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 in Portuguese ('Marca uma tarefa como concluída') that directly states the tool's purpose with zero waste. It's appropriately sized and front-loaded, making it easy for an agent 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 this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., what happens on success/failure), return values, or error conditions, which are critical for an agent to use it correctly in context with siblings.

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 schema description coverage is 100%, with both parameters (listTitle and taskTitle) documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., it doesn't explain how to identify the task or list). Baseline 3 is appropriate when the schema does the heavy lifting.

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 'Marca uma tarefa como concluída' clearly states the action (marks as completed) and the resource (a task). It's specific about what the tool does, though it doesn't explicitly differentiate from sibling tools like todo_add or todo_create, which would require a 5.

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. It doesn't mention prerequisites (e.g., the task must exist), exclusions, or comparisons to siblings like todo_list or todo_show, leaving the agent without contextual usage information.

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/hevener10/mcp-todo-checklist'

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