Skip to main content
Glama

create_task

Create a Kanboard task in a specified project with title, description, tags, due date, owner, priority, and column; defaults to the project's first column when no column is set.

Instructions

Create a task. Defaults to the project's first column.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "title": "<title>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
titleYes
columnNo
due_dateNo
owner_idNoAssignee user ID
priorityNo
project_idYesKanboard project ID
descriptionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world write, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the task is placed in the project's first column when no column is given. It says nothing about required permissions, what happens on invalid project_id, or whether the new task is immediately visible.

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?

Two short sentences, front-loaded with the action and with no filler or repetition. Brevity here edges toward under-specification rather than verbosity, which is penalized elsewhere rather than in this dimension.

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?

An output schema exists, so return values need not be described, but eight parameters with wide gaps in owner, priority, tags, and due-date semantics are left entirely to the sparse schema. For a creation tool with this many fields, the description omits too much for an agent to call it confidently.

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 only 25% for 8 parameters, so the description carries the burden — yet it explains only the column-default case and never mentions title, tags, owner_id, priority, due_date, or description. Required parameters (project_id, title) are undocumented in the description beyond their names.

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?

States a specific verb and resource ('Create a task') that is immediately recognizable, and hints at where the task lands by default. It does not differentiate itself from the close sibling create_subtask, so an agent must infer the distinction from names alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as create_subtask or update_task. The only contextual hint is the default-column behavior, which is about invocation, not tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.