Skip to main content
Glama
delega-dev

delega-mcp

by delega-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_task

Create a new task with title, due date, priority, labels, and project assignment to delegate work and track progress in AI agent workflows. Optionally require completion evidence.

Instructions

Create a new task in Delega

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelsNoLabels to apply
contentYesTask title / content
due_dateNoDue date in YYYY-MM-DD format
priorityNoPriority: 1=normal, 2=medium, 3=high, 4=urgent
project_idNoProject ID to assign to
descriptionNoDetailed description
evidence_policyNoSet 'required' to force structured completion evidence (commit/PR/CI/etc.) before this task can be completed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.19.0
    • removedInput schema / properties / project_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / project_id / type
      Added value: +[
+  "string",
+  "number"
+]
  2. Changed1 schema field changedv1.13.1
    • addedInput schema / properties / evidence_policy
      Added value: +{
+  "description": "Set 'required' to force structured completion evidence (commit/PR/CI/etc.) before this task can be completed",
+  "enum": [
+    "required"
+  ],
+  "type": "string"
+}
  3. Changed4 schema fields changedv1.9.0
    • addedInput schema / properties / project_id / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  }
+]
    • removedInput schema / properties / project_id / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / project_id / minimum
      Removed value: --9007199254740991
    • removedInput schema / properties / project_id / type
      Removed value: -"integer"
  4. Changed3 schema fields changedv1.2.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / project_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / project_id / minimum
      Added value: +-9007199254740991
  5. First observedv1.0.3

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing. It does not state whether creation is idempotent, how duplicate tasks are handled (despite a find_duplicate_tasks sibling), what permissions are needed, or what happens if project_id is invalid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words, but for a 7-parameter creation tool with no annotations or output schema it is under-specified rather than genuinely concise. There is nothing to front-load or structure.

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?

Given a 7-parameter mutation tool with no annotations and no output schema, the description is inadequate. It should at least mention required fields, defaults, or the effect of evidence_policy and duplicate handling, none of which appear.

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 100%, so the schema already documents all 7 parameters including the priority enum and evidence_policy. The description adds nothing beyond that, which is the expected baseline when the schema does the heavy lifting.

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 clear verb+resource: 'Create a new task'. An agent immediately knows this creates a task. However, it offers no differentiation from siblings like create_recurring_task or delegate_task, which also produce task-like objects, so an agent must infer which creator to pick.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as create_recurring_task or delegate_task. The agent receives no signal about when this tool is the right choice versus its siblings.

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