Skip to main content
Glama
IlyaIvanchikov

weeek-mcp-smart

by IlyaIvanchikov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

weeek_create_tasks

Create up to 50 WEEEK tasks in one call, each validated separately. Batch task creation that returns per-item success or error results so one bad name does not abort the rest.

Instructions

Create up to 50 WEEEK tasks in one call. Each item takes the same fields as weeek_create_task: title and project (name or id) are required; column, assignee, due, description, priority, type, parent and fields are optional. Items are created in order and one bad name does not abort the batch: the reply is one entry per item, { ok: true, task } or { ok: false, error, candidates? }.

Input Schema

NameRequiredDescriptionDefault
tasksYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / tasks / items / properties / fields / description
      Previous value: -"Custom-field values by field name or id. text/link: a string; number: a number; boolean: true/false; datetime: a natural-language date or time; select: an option name; multiselect: option names; member/approval: member names; contact: a contact id; null clears the field."New value: +"Custom-field values by field name or id. text/link: a string; number: a number; boolean: true/false; datetime: a natural-language date or time; select: an option name; multiselect: option names; member/approval: member names; contact: a contact name or id; null clears the field."
  2. Changed4 schema fields changedv0.7.0
    • addedInput schema / properties / tasks / items / properties / fields
      Added value: +{
+  "additionalProperties": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      },
+      {
+        "type": "boolean"
+      },
+      {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      {
+        "type": "null"
+      }
+    ]
+  },
+  "description": "Custom-field values by field name or id. text/link: a string; number: a number; boolean: true/false; datetime: a natural-language date or time; select: an option name; multiselect: option names; member/approval: member names; contact: a contact id; null clears the field.",
+  "type": "object"
+}
    • addedInput schema / properties / tasks / items / properties / parent
      Added value: +{
+  "description": "Id of the task this one becomes a subtask of.",
+  "type": "integer"
+}
    • addedInput schema / properties / tasks / items / properties / priority
      Added value: +{
+  "enum": [
+    "low",
+    "medium",
+    "high",
+    "hold"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / tasks / items / properties / type
      Added value: +{
+  "enum": [
+    "action",
+    "meet",
+    "call"
+  ],
+  "type": "string"
+}
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: creation order, non-atomic failure semantics ("one bad name does not abort the batch"), and the exact per-item reply shape including the error/candidates variant. It omits permissions and rate-limit context, so it is strong but not exhaustive.

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 dense sentences, no filler: batch capability first, then field contract, then failure/return behavior. Every clause carries information an agent needs.

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?

There is no output schema, and the description steps in by describing the per-item response contract (`{ ok: true, task }` / `{ ok: false, error, candidates? }`), which is exactly what an agent needs to parse results. Auth requirements and any batch size/rate constraints are the remaining gap.

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?

Top-level schema description coverage is 0%, so the description must compensate, and it does: it names the required fields (`title`, `project`, with name-or-id accepted) and enumerates all optional ones. It adds meaning beyond the schema, though it does not explain value formats for fields like `due` or `column` beyond what nested schema text provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (create), resource (WEEEK tasks) and scope (up to 50 in one call), which cleanly separates it from the single-item sibling weeek_create_task. An agent can tell exactly what this does without opening the schema.

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?

The batch framing ("up to 50 ... in one call") makes the intended usage clear and implicitly routes single-task creation to weeek_create_task, which it names. It stops short of an explicit when-to-use/when-not rule, so it is clear context rather than full routing guidance.

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