Skip to main content
Glama
aafsar

Task Manager MCP Server

by aafsar

create_task

Add new tasks to your task management system by specifying title, description, priority, category, and due date for organized tracking.

Instructions

Create a new task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title (required)
descriptionNoDetailed description
priorityNoTask prioritymedium
categoryNoTask category (work/personal/etc)
dueDateNoDue date in YYYY-MM-DD format

Implementation Reference

  • The core handler function for the 'create_task' tool. Validates input using CreateTaskSchema, generates a new task with UUID, adds it to storage, and returns a formatted success message.
    export async function createTask(args: unknown) {
      // Validate input
      const validated = CreateTaskSchema.parse(args);
    
      // Load existing tasks
      const storage = await loadTasks();
    
      // Create new task
      const newTask: Task = {
        id: uuidv4(),
        title: validated.title,
        description: validated.description,
        priority: validated.priority as Priority,
        category: validated.category,
        dueDate: validated.dueDate,
        status: "pending",
        createdAt: new Date().toISOString(),
      };
    
      // Add to storage
      storage.tasks.push(newTask);
      await saveTasks(storage);
    
      return {
        content: [
          {
            type: "text",
            text: `✅ Task created successfully!\n\n${formatTask(newTask)}`,
          },
        ],
      };
    }
  • Zod schema used for input validation in the createTask handler.
    export const CreateTaskSchema = z.object({
      title: z.string().min(1, "Title is required"),
      description: z.string().optional(),
      priority: z.enum(["low", "medium", "high"]).default("medium"),
      category: z.string().optional(),
      dueDate: z
        .string()
        .regex(/^\d{4}-\d{2}-\d{2}$/, "Date must be YYYY-MM-DD")
        .optional(),
    });
  • src/index.ts:26-57 (registration)
    Tool registration in the TOOLS array, defining name, description, and JSON inputSchema for the MCP ListTools request.
    {
      name: "create_task",
      description: "Create a new task",
      inputSchema: {
        type: "object",
        properties: {
          title: {
            type: "string",
            description: "Task title (required)",
          },
          description: {
            type: "string",
            description: "Detailed description",
          },
          priority: {
            type: "string",
            enum: ["low", "medium", "high"],
            default: "medium",
            description: "Task priority",
          },
          category: {
            type: "string",
            description: "Task category (work/personal/etc)",
          },
          dueDate: {
            type: "string",
            pattern: "^\\d{4}-\\d{2}-\\d{2}$",
            description: "Due date in YYYY-MM-DD format",
          },
        },
        required: ["title"],
      },
  • src/index.ts:215-216 (registration)
    Dispatch handler in the switch statement that routes 'create_task' calls to the createTask function.
    case "create_task":
      return await createTask(args);
  • src/index.ts:13-14 (registration)
    Import of the createTask handler from './tools.js'.
    createTask,
    listTasks,
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Create a new task', implying a write/mutation operation, but doesn't disclose behavioral traits such as permissions needed, whether creation is idempotent, error handling, or what happens on success (e.g., returns a task ID). This is a significant gap 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 with zero waste: 'Create a new task'. It's appropriately sized and front-loaded, making it easy to parse quickly without unnecessary elaboration.

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 doesn't explain what the tool returns (e.g., a task object or ID), error conditions, or system-specific context (e.g., where tasks are stored). For a 5-parameter tool with rich schema but missing behavioral context, this is inadequate.

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?

Schema description coverage is 100%, with all parameters well-documented in the schema (e.g., title as required, priority enum, due date format). The description adds no parameter semantics beyond what the schema provides, so it meets the baseline of 3 where the schema does the heavy lifting.

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 'Create a new task' clearly states the action (create) and resource (task), which is adequate. However, it doesn't distinguish this tool from sibling tools like 'update_task' or specify what kind of task system this is (e.g., todo list, project management). It's not tautological but remains somewhat vague about scope.

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., authentication), when not to use it (e.g., for updating existing tasks), or refer to sibling tools like 'update_task' for modifications. This leaves the agent without contextual usage cues.

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/aafsar/task-manager-mcp-server'

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