Skip to main content
Glama
0Thomas1

Kanban MCP Server

by 0Thomas1

add-tag

Add tags to Kanban tasks to organize and categorize work items for better workflow management and tracking.

Instructions

add tags to a tasks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
task_tagYes
task_idYes

Implementation Reference

  • src/index.ts:169-193 (registration)
    Registration of the 'add-tag' MCP tool. Includes input schema (task_id: string, task_tag: string), inline handler that calls addTaskTag utility and returns success/error message.
    server.tool("add-tag", "add tags to a tasks",{
        task_tag: z.string(),
        task_id: z.string()
    },async (params)=>{
        try {
            await mongooseUtils.addTaskTag(params.task_id,params.task_tag);
            return{
                content: [
              {
                type: "text",
                text: `Added tag "${params.task_tag}" to tasks"${params.task_id}" successfully.`,
              },
            ],
            }
        } catch {
            return{
                content: [
              {
                type: "text",
                text: `Failed to add tag "${params.task_tag}" to tasks"${params.task_id}".`,
              },
            ],
            }
        }
    });
  • Core implementation of adding a tag to a task. Finds task by ID, adds lowercase tag if not already present, and persists to MongoDB.
    export async function addTaskTag(taskId: string, tag: string) {
      try {
        const task = await Task.findById(taskId);
        if (!task) {
          throw new Error("Task not found");
        }
    
        if (!task.tags.includes(tag.toLowerCase())) {
          task.tags.push(tag.toLowerCase());
          await task.save();
        }
      } catch {
        throw new Error("Failed to add tag");
      }
    }
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 the tool adds tags, implying a mutation operation, but doesn't disclose behavioral traits like whether tags are appended or replaced, if there are rate limits, permission requirements, or what happens on success/failure. The description adds minimal value beyond the basic action.

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 very concise (three words) and front-loaded with the core action. However, the grammatical error ('tasks' instead of 'task') slightly reduces clarity. It earns its place by stating the purpose but could be more polished.

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 no annotations, no output schema, and 0% schema description coverage for a mutation tool with 2 parameters, the description is incomplete. It lacks details on behavior, parameter meanings, return values, and error handling, leaving significant gaps for the agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema provides no parameter documentation. The description mentions 'tags' and 'tasks' but doesn't explain what 'task_tag' and 'task_id' parameters represent, their formats, or constraints. It adds minimal semantic value beyond what's inferable from parameter names.

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 states the action ('add tags') and target ('to a tasks'), but has grammatical issues ('tasks' should be singular) and lacks specificity about what kind of tags or tasks. It distinguishes from siblings like 'create-task' and 'move-task' by focusing on tagging rather than creation or movement, but doesn't clearly differentiate from potential tagging alternatives.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., task must exist), exclusions, or comparisons with sibling tools. The agent must infer usage from the tool name alone.

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