Skip to main content
Glama
hevener10

MCP TODO Checklist Server

by hevener10

todo_add

Add a new task to a checklist with title, priority, due date, and tags for organized task management.

Instructions

Adiciona uma nova tarefa à lista

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
listTitleYesTítulo da lista
taskTitleYesTítulo da tarefa
priorityNoPrioridade da tarefa
dueDateNoData de vencimento (YYYY-MM-DD)
tagsNoTags da tarefa

Implementation Reference

  • Main handler logic for the 'todo_add' tool: parses arguments with addSchema, retrieves user checklists to find the target list, adds a new item via checklistService.addItem, and returns success message.
    case "todo_add": {
      console.error('DEBUG - Processing todo_add');
      const params = addSchema.parse(args);
      const lists = await checklistService.getUserChecklists('current-user');
      const list = lists.find(l => l.title === params.listTitle);
      
      if (!list) {
        throw new Error(`Lista não encontrada: ${params.listTitle}`);
      }
    
      const newItem = await checklistService.addItem(list.id, {
        title: params.taskTitle,
        priority: params.priority,
        dueDate: params.dueDate ? new Date(params.dueDate) : undefined,
        tags: params.tags,
        completed: false
      });
      return { content: [{ type: "text", text: `Tarefa "${params.taskTitle}" adicionada à lista "${params.listTitle}"!` }] };
    }
  • Zod validation schema used in the todo_add handler for input parameters.
    const addSchema = z.object({
      listTitle: z.string(),
      taskTitle: z.string(),
      priority: z.enum(['low', 'medium', 'high']).optional().default('medium'),
      dueDate: z.string().optional(),
      tags: z.array(z.string()).optional().default([])
    });
  • src/index.ts:111-125 (registration)
    Tool registration in the ListTools response, including name, description, and JSON input schema.
    {
      name: "todo_add",
      description: "Adiciona uma nova tarefa à lista",
      inputSchema: {
        type: "object",
        properties: {
          listTitle: { type: "string", description: "Título da lista" },
          taskTitle: { type: "string", description: "Título da tarefa" },
          priority: { type: "string", enum: ["low", "medium", "high"], description: "Prioridade da tarefa" },
          dueDate: { type: "string", description: "Data de vencimento (YYYY-MM-DD)" },
          tags: { type: "array", items: { type: "string" }, description: "Tags da tarefa" },
        },
        required: ["listTitle", "taskTitle"],
      },
    },
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. While 'Adiciona' implies a write/mutation operation, the description doesn't disclose any behavioral traits like whether this requires specific permissions, what happens on duplicate tasks, whether the operation is idempotent, or what the response looks like. For a mutation tool with zero annotation coverage, this 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 in Portuguese that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded with the core functionality.

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?

For a mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what happens after adding a task, what the return value might be, or any error conditions. The description alone doesn't provide enough context for an agent to understand the full implications of using this tool.

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 all 5 parameters well-documented in the schema itself. The description adds no parameter information beyond what's already in the schema, so it doesn't enhance parameter understanding. With high schema coverage, the baseline score of 3 is appropriate.

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 ('Adiciona' - adds) and resource ('uma nova tarefa à lista' - a new task to the list), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'todo_create', which appears to serve a similar purpose based on naming, leaving some ambiguity about differentiation.

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 'todo_create' or 'todo_list'. There's no mention of prerequisites, constraints, or appropriate contexts for this specific add operation versus other todo-related tools.

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