Skip to main content
Glama
0Thomas1

Kanban MCP Server

by 0Thomas1

create-task

Add new todo tasks to your Kanban board by specifying a title and description for organized project management.

Instructions

create a new todo task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_titleYes
descriptionYes

Implementation Reference

  • src/index.ts:41-74 (registration)
    Registration of the 'create-task' MCP tool, including name, description, Zod input schema, metadata hints, and inline handler function that delegates to mongooseUtils.createTask.
    server.tool(
      "create-task",
      "create a new todo task",
      {
        task_title: z.string(),
        description: z.string(),
      },
      {
        title: "create a todo task",
        readonlyHint: false,
        destructiveHint: false,
        idempotentHint: false,
        openWorldHint: true,
      },
      async (params) => {
        try {
          await mongooseUtils.createTask(params);
          return {
            content: [
              {
                type: "text",
                text: `Task "${params.task_title}" created successfully!`,
              },
            ],
          };
        } catch {
          return {
            content: [
              { type: "text", text: "An error occurred while creating the task." },
            ],
          };
        }
      }
    );
  • Inline handler function for the 'create-task' tool. It calls the createTask utility, returns a success message with task title, or error message on failure.
    async (params) => {
      try {
        await mongooseUtils.createTask(params);
        return {
          content: [
            {
              type: "text",
              text: `Task "${params.task_title}" created successfully!`,
            },
          ],
        };
      } catch {
        return {
          content: [
            { type: "text", text: "An error occurred while creating the task." },
          ],
        };
      }
    }
  • Zod input schema for the 'create-task' tool defining required string parameters: task_title and description.
    {
      task_title: z.string(),
      description: z.string(),
    },
  • Helper utility function createTask that creates a new MongoDB Task document with default 'todo' status and associates it with the current user.
    export interface CreateTaskParams {
      task_title: string;
      description: string;
    }
    
    export async function createTask(params: CreateTaskParams): Promise<void> {
      const newTask = await Task.create({
        title: params.task_title,
        description: params.description,
        taskStatus: "todo",
      });
    
      // You may need to adjust how you get the user
      const user = await User.findOne({
        username: username,
      });
    
      if (user) {
        newTask.user = user;
        await newTask.save();
        user.tasks.push(newTask);
        await user.save();
      }
    }
Behavior3/5

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

Annotations indicate openWorldHint=true, idempotentHint=false, and destructiveHint=false, which the description doesn't contradict. The description adds minimal behavioral context by implying creation of a new entity, but it doesn't elaborate on permissions, side effects, or response format. With annotations covering key traits, the description adds some value but lacks depth.

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 no wasted words. It's front-loaded and directly states the action, making it easy to parse quickly. This is an example of appropriate brevity for a straightforward tool.

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 lack of output schema and minimal parameter details, the description is incomplete. It doesn't cover what the tool returns, error conditions, or how it interacts with the system. For a creation tool with no output schema, more context on the result or usage would be beneficial.

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 input schema has two required parameters with 0% description coverage, so the schema provides no semantic details. The description doesn't explain what 'task_title' or 'description' represent, their formats, or constraints. However, for a simple creation tool with only two parameters, the baseline is adequate but leaves room for improvement.

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 todo task' clearly states the verb ('create') and resource ('todo task'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'add-tag' or 'move-task' beyond the basic action, and the title annotation repeats the same phrase, making it somewhat redundant rather than distinctive.

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, such as needing an existing task list, or compare it to siblings like 'add-tag' for modifying tasks. This leaves the agent with no context for selection beyond the tool name.

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/0Thomas1/Kanban-MCP'

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