Skip to main content
Glama
adalekin

weeek-mcp

by adalekin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

weeek_create_task

Create a task in a Weeek project by providing a title and project ID, optionally assigning a board column, assignee, and priority. Set dates separately.

Instructions

Create a task. Requires a project_id (and normally a board_column_id, which you get from weeek_list_board_columns). Dates are set separately via weeek_update_task.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayNoY-m-d
typeNo
titleYes
user_idNoAssignee id
priorityNoPriority as a number or a label: 0 low (Низкий), 1 medium (Средний), 2 high (Высокий), 3 hold (Замороженный).
parent_idNoParent task id for a subtask
project_idYes
descriptionNoTask description as HTML, which is what Weeek's create endpoint stores. weeek_update_task takes Markdown instead, because it writes through the editor rather than REST.
custom_fieldsNoCustom field values keyed by field id (names only work on an existing task, via weeek_update_task) — get the ids from weeek_list_custom_fields. For a select field pass the option id. A field that does not belong to this project is reported as an error.
board_column_idNoTarget column; null puts the task in the board default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.2.2
    • addedInput schema / properties / board_column_id / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / board_column_id / type
      Removed value: -[
-  "integer",
-  "null"
-]
    • addedInput schema / properties / priority / anyOf
      Added value: +[
+  {
+    "enum": [
+      0,
+      1,
+      2,
+      3
+    ],
+    "type": "integer"
+  },
+  {
+    "enum": [
+      "low",
+      "medium",
+      "high",
+      "hold"
+    ],
+    "type": "string"
+  }
+]
    • removedInput schema / properties / priority / enum
      Removed value: -[
-  0,
-  1,
-  2,
-  3,
-  "low",
-  "medium",
-  "high",
-  "hold"
-]
    • removedInput schema / properties / priority / type
      Removed value: -[
-  "integer",
-  "string"
-]
  2. First observedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that dates are set separately and that board_column_id is normally required, which are non-obvious traits. However, it says nothing about permissions, failure modes, or what the call returns, leaving meaningful gaps for a mutation tool with zero annotation coverage.

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?

Three compact sentences with no filler, front-loading the create action and then the key prerequisites and the date caveat. Every sentence carries actionable information.

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?

For a 10-parameter create tool with no output schema and no annotations, the description covers the essential prerequisites and the important date-handling quirk. Parameter details are largely carried by a 70%-covered schema, so it is reasonably complete, though it omits return/error behavior.

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 70%, and the schema itself documents day, priority, description, custom_fields, and board_column_id richly. The description adds the project_id/board_column_id requirements but little else, so it largely defers to the schema. Baseline for this coverage level is around 3.

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?

The first sentence states a specific verb and resource ('Create a task'), which cleanly separates it from update/delete/move siblings. It also implies scope by tying creation to a project. It stops short of a fuller differentiation narrative, but the core purpose is unambiguous.

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 tells the agent what is required (project_id), what is normally needed (board_column_id) and where to get it (weeek_list_board_columns), plus that dates must be set via weeek_update_task. This is real operational guidance. It lacks an explicit 'when not to use this' or a named alternative for other creation paths, so it is not a full 5.

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

Deploy Server

Other Tools