Skip to main content
Glama
0Thomas1

Kanban MCP Server

by 0Thomas1

set-prioity

Update task priority levels (low, medium, high) in a Kanban system to manage workflow and focus on important items.

Instructions

set a task to a different priority

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_idYes
new_priorityYes

Implementation Reference

  • Inline handler function for the 'set-prioity' MCP tool. It calls the helper function setTaskPriority and formats success/error responses.
    async (params) => {
      try {
        await mongooseUtils.setTaskPriority(params.task_id, params.new_priority);
        return {
          content: [
            {
              type: "text",
              text: `Set task "${params.task_id}" Priority to "${params.new_priority}" successfully!`,
            },
          ],
        };
      } catch {
        return {
          content: [
            {
              type: "text",
              text: `Failed to set task "${params.task_id}" priority to "${params.new_priority}".`,
            },
          ],
        };
      }
    }
  • Zod input schema for the 'set-prioity' tool defining task_id and new_priority parameters.
      task_id: z.string(),
      new_priority: z.enum(["low", "medium", "high"]),
    },
  • src/index.ts:115-151 (registration)
    Registration of the 'set-prioity' tool using server.tool, including name, description, schema, hints, and handler.
    server.tool(
      "set-prioity",
      "set a task to a different priority",
      {
        task_id: z.string(),
        new_priority: z.enum(["low", "medium", "high"]),
      },
      {
        title: "set a task to a different priority",
        readonlyHint: false,
        destructiveHint: false,
        idempotentHint: false,
        openWorldHint: true,
      },
      async (params) => {
        try {
          await mongooseUtils.setTaskPriority(params.task_id, params.new_priority);
          return {
            content: [
              {
                type: "text",
                text: `Set task "${params.task_id}" Priority to "${params.new_priority}" successfully!`,
              },
            ],
          };
        } catch {
          return {
            content: [
              {
                type: "text",
                text: `Failed to set task "${params.task_id}" priority to "${params.new_priority}".`,
              },
            ],
          };
        }
      }
    );
  • Helper function that performs the actual database update for task priority using Mongoose Task model.
    export async function setTaskPriority(
      taskId: string,
      priority: "low" | "medium" | "high"
    ) {
      try {
        const task = await Task.findById(taskId);
        if (!task) {
          throw new Error("Task not found");
        }
    
        task.priority = priority;
        await task.save();
      } catch {
        throw new Error("Failed to set priority");
      }
    }
Behavior3/5

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

Annotations provide hints (openWorldHint: true, idempotentHint: false, destructiveHint: false), covering safety and idempotency. The description adds no behavioral context beyond this, such as error handling, permission requirements, or side effects. It doesn't contradict annotations, but fails to supplement them with additional insights.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized for a simple tool, though it could be more informative without sacrificing brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (2 parameters, no output schema) and annotations covering key hints, the description is minimally adequate. It states what the tool does but lacks details on outcomes, error cases, or integration with siblings, leaving gaps in contextual understanding for effective use.

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 0%, so the description must compensate, but it only implies parameters without detailing them. It mentions 'task' and 'priority', aligning with 'task_id' and 'new_priority', but adds no meaning beyond the schema's enum for priority or task_id format. Baseline 3 is appropriate as the schema defines parameters clearly despite low coverage.

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 'set a task to a different priority' clearly states the action (set) and resource (task priority), but it's vague about scope and doesn't distinguish from siblings like 'move-task' or 'add-tag'. It restates the title verbatim, lacking specificity beyond the basic operation.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., task must exist), exclusions, or compare to siblings like 'move-task' for context changes. The description offers only the basic function without contextual usage advice.

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