Skip to main content
Glama

create_task

Create a project task with assignees, board column, reminder, deadline, checklist and comment. Assignees get notified and a task card can be posted to the project chat.

Instructions

Create a task in a project. Assignees get notified: confirm with the user first unless they asked for exactly this task.

project: id or title (required: Mizito has no project-less tasks). board: kanban column title/id (default: the project's first column). assignees: names/ids/"me"; default ["me"]; [] = nobody. reminder: when the task is scheduled ("زمان یادآوری"): this is the date Mizito uses for today / overdue. "2026-11-20 14:30" | "1405/08/30 14:30". deadline: "مهلت انجام", only in projects with the deadline feature. checklist: item titles. comment: first comment text. post_card_to_project_chat: put a task card into the project chat. Default: yes when the project has a chat, like the web app. Later changes to the task show up in the chat only if it has this card.

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": {
      "title": "<title>",
      "project": "<project>"
    },
    "name": "create_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardNo
notesNo
titleYes
labelsNo
commentNo
projectYes
deadlineNo
reminderNo
assigneesNo
checklistNo
post_card_to_project_chatNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare the coarse profile (non-readonly, non-idempotent, non-destructive), so the description carries real weight and does: it discloses the notification side effect on assignees, the post_card_to_project_chat behavior and its lasting effect on whether later task changes surface in chat, and the constraint that deadline only works in projects with the deadline feature. These are exactly the side effects an agent could not infer from structured fields.

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 front-loaded with the action and the confirmation caveat, then switches to a compact parameter-key list with no filler sentences. The reminder entry is slightly rambling with its embedded translation and format examples, but nearly every clause carries operational meaning.

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

Completeness4/5

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

Return values need not be described because an output schema exists, and the mutation's side effects and defaults are covered thoroughly. The remaining shortfall is that two schema parameters (labels, notes) get no semantic guidance at all, which matters in a tool with eleven parameters.

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

Parameters4/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, and it does for most of the 11 parameters: it explains id-or-title for project, title/id with default for board, the name/id/"me" forms and [] meaning nobody for assignees, plus the date formats and Persian field aliases for reminder and deadline. notes and labels are left entirely undocumented, and title is only implicitly covered, which is the one real gap.

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?

"Create a task in a project" states a specific verb plus resource, and the parenthetical that Mizito has no project-less tasks clarifies the required scope. It does not explicitly route the agent away from siblings such as update_task or the more granular set_task_deadline/set_task_reminder, but the create-vs-modify distinction is unambiguous from the verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete behavioral rule for when to proceed: assignees get notified, so confirm with the user first unless they asked for exactly this task. It also sets expectations for defaults (assignees default to ["me"], board defaults to the first column). It stops short of naming alternatives for narrower operations, so there is no explicit when-not-to-use clause.

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