Skip to main content
Glama

Weft

by com.letsweft
OverviewDiscussionsAdmin

Create Task

create_task

Use this when the user says 'add a task', 'remind me to …', or otherwise asks to capture work. If columnId is omitted the task goes to the Backlog. Priority defaults to medium unless urgency is implied (use 'high' for words like urgent/asap, 'low' for nice-to-have).

Input Schema

NameRequiredDescriptionDefault
dueAtNoThe day this is due, as an ISO date-time (only the date part is used, e.g. "2026-10-31T00:00:00Z"). Put a date on anything the user said has a deadline or a day to check back — dated tasks show on the user's Weft calendar and in their subscribed Google/Apple/Outlook calendar. Pass null to clear.
titleYes
projectNoProject name (case-insensitive) or project ID
startAtNoThe day work begins, same format as dueAt. With dueAt it makes a span on the calendar ("measure 5–12 November"); never after dueAt. Pass null to clear.
assigneeNoExecutor: a member's name or email (case-insensitive), 'me' to assign to yourself (the calling agent), or 'none' to unassign
columnIdNo
priorityNomedium
sprintIdNo
blockedByNoTasks that must finish before this one can start. The task derives agentState "blocked" while any of them is open, leaves ready-sets, and unblocks itself the moment the last blocker completes. Cycles are refused.
descriptionNo
verificationNoHow to verify this task is actually done — the server executes these checks on complete_task. {mode, checks[]}: mode "executable"/"state_delta" lets fully-passed work move to Done by itself; "checklist"/"human" always stops at the user. Check kinds: http (GET url → expected status, optional mustContain phrase), citation (url + quote that must appear on the page), string_check (receipt must contain/equal/match value), file_hash (an artifact must carry this sha256), human_checklist (items only a person can judge — resolved when they accept). Give every task at least one machine check when you can: unverifiable "done" is the failure mode this board exists to close.
requiresReviewNoStop at the user before this is called done. Set it ONLY for the irreversible: money, publishing outward, production, anything legal. Everything else finishes without them — a queue everything enters is a queue nobody reads.
estimateMinutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / dueAt / description
      Added value: +"The day this is due, as an ISO date-time (only the date part is used, e.g. \"2026-10-31T00:00:00Z\"). Put a date on anything the user said has a deadline or a day to check back — dated tasks show on the user's Weft calendar and in their subscribed Google/Apple/Outlook calendar. Pass null to clear."
    • addedInput schema / properties / startAt
      Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The day work begins, same format as dueAt. With dueAt it makes a span on the calendar (\"measure 5–12 November\"); never after dueAt. Pass null to clear."
+}
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observed

TDQS

A3.9/5.0
Behavior4/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 mutation. The description adds useful behavioral defaults beyond the annotations: omitted columnId goes to Backlog, and priority defaults to medium with urgency heuristics. It still omits permissions, response shape, and creation side effects.

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?

The description is three efficient sentences, front-loads the invocation trigger, then covers notable defaults. Every sentence earns its place with no redundancy.

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

Completeness3/5

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

For a 13-parameter tool with nested verification and many siblings, the description covers basic invocation and two defaults but omits advanced parameters, sibling routing, and return-value expectations. The schema carries much of the complex parameter detail, but the description is not complete for this level of complexity.

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?

The description adds meaning for columnId and priority beyond the schema, including default routing and a heuristic for priority selection. However, with 13 parameters and only 54% schema description coverage, several parameters such as sprintId, description, and estimateMinutes are not explained in either place.

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 description states a specific action (capturing/creating a task) and gives concrete user trigger phrases such as 'add a task' and 'remind me to'. It does not explicitly distinguish this from siblings like bulk_create_tasks or add_task_to_sprint, so it is clear but not fully differentiated.

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 explicit when-to-use guidance via trigger phrases and adds a priority heuristic for urgency terms. It does not state when not to use it or route multi-task/sprint-specific cases to sibling tools, so it is strong but incomplete.

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

All Weft toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources