Skip to main content
Glama
hevener10

MCP TODO Checklist Server

by hevener10

todo_create

Create a new task list with a title and optional description to organize and manage your to-do items.

Instructions

Cria uma nova lista de tarefas

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTítulo da lista
descriptionNoDescrição da lista (opcional)

Implementation Reference

  • Executes the todo_create tool: validates input using createSchema, calls checklistService.createChecklist to persist a new todo list, and returns a success response.
    case "todo_create": {
      console.error('DEBUG - Processing todo_create');
      const params = createSchema.parse(args);
      const newList = await checklistService.createChecklist({
        title: params.title,
        description: params.description,
        owner: 'current-user',
        items: []
      });
      return { content: [{ type: "text", text: `Lista "${params.title}" criada com sucesso!` }] };
    }
  • Zod schema for validating input parameters of todo_create tool (title required, description optional).
    const createSchema = z.object({
      title: z.string(),
      description: z.string().optional()
    });
  • src/index.ts:99-110 (registration)
    Registers the todo_create tool in the listTools response, including name, description, and input schema.
    {
      name: "todo_create",
      description: "Cria uma nova lista de tarefas",
      inputSchema: {
        type: "object",
        properties: {
          title: { type: "string", description: "Título da lista" },
          description: { type: "string", description: "Descrição da lista (opcional)" },
        },
        required: ["title"],
      },
    },
  • Core helper method that creates and persists a new Checklist object with generated UUID, timestamps, and empty items array.
    async createChecklist(data: Omit<Checklist, 'id' | 'createdAt' | 'updatedAt'>): Promise<Checklist> {
      const now = new Date();
      const checklist: Checklist = {
        ...data,
        id: crypto.randomUUID(),
        createdAt: now,
        updatedAt: now,
        items: []
      };
    
      await this.storage.save(`checklist:${checklist.id}`, checklist);
      return checklist;
    }
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 tool creates a new task list, implying a write operation, but lacks details on permissions required, whether creation is idempotent, error handling (e.g., if a list with the same title exists), or response format (since no output schema exists). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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: 'Cria uma nova lista de tarefas.' It's front-loaded with the core action and resource, with no wasted words or redundant information. This makes it easy to parse quickly, though its brevity contributes to gaps in other dimensions like guidelines and transparency.

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 complexity (a write operation with no annotations and no output schema), the description is incomplete. It doesn't address behavioral aspects like authentication needs, error conditions, or what happens on success (e.g., returns a list ID). With siblings like 'todo_list' and 'todo_show', more context on how this tool fits into the workflow is missing, leaving users under-informed.

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 doesn't add any parameter-specific information beyond what the input schema provides. The schema has 100% description coverage, with clear docs for 'title' and 'description', so the baseline is 3. The description doesn't explain parameter interactions (e.g., how title uniqueness is handled) or provide examples, but it doesn't need to compensate for schema gaps either.

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 tool's purpose: 'Cria uma nova lista de tarefas' (Creates a new task list). It specifies the verb 'cria' (creates) and the resource 'lista de tarefas' (task list), making the action and target explicit. However, it doesn't differentiate from sibling tools like 'todo_add' (which likely adds items to an existing list) or 'todo_list' (which likely lists existing lists), leaving some ambiguity about when to choose this tool over others.

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., whether authentication is needed), exclusions (e.g., cannot create duplicate lists), or comparisons to siblings like 'todo_add' (for adding tasks) or 'todo_list' (for viewing lists). Without such context, users must infer usage from the tool name alone, which is insufficient for optimal 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/hevener10/mcp-todo-checklist'

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