Skip to main content
Glama
delega-dev

delega-mcp

by delega-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delegate_task

Delegate work by creating a child task linked to a parent, marking the parent as delegated. Use it for multi-agent handoffs so the delegation chain is recorded.

Instructions

Delegate a task: create a child task linked to a parent. The parent's status flips to 'delegated'. Use this (not assign_task) for multi-agent handoffs so the delegation chain is recorded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelsNoLabels to apply
contentYesChild task title / content
task_idYesParent task ID to delegate from
due_dateNoDue date in YYYY-MM-DD format
priorityNoPriority: 1=normal, 2=medium, 3=high, 4=urgent
project_idNoProject ID (admin only for non-self delegations)
descriptionNoDetailed description
assigned_to_agent_idNoAgent ID to assign the child task to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.19.0
    • removedInput schema / properties / assigned_to_agent_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / assigned_to_agent_id / type
      Added value: +[
+  "string",
+  "number"
+]
    • removedInput schema / properties / project_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / project_id / type
      Added value: +[
+  "string",
+  "number"
+]
    • removedInput schema / properties / task_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  }
-]
    • addedInput schema / properties / task_id / type
      Added value: +[
+  "string",
+  "number"
+]
  2. 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"
  3. Addedv1.2.1

TDQS

A4.2/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 does disclose one meaningful side effect beyond the schema – the parent's status flips to 'delegated' – which is exactly the kind of trait an agent needs. However it says nothing about permissions (the schema mentions admin-only for non-self delegations), reversibility/undo, or failure modes for a mutation tool.

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?

Two sentences, zero filler, with the core action and the sibling exclusion front-loaded. Every clause earns its place.

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 an 8-parameter mutation with a rich schema and no output schema, the description covers purpose, the alternative to use instead, and the key state change. It stops short of telling the agent what the call returns (e.g., the new child task ID), which is the one gap given no output schema exists.

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 all 8 parameters are already documented in the schema, including the priority enum and admin-only project_id note. The description adds no additional parameter syntax or format guidance, so the baseline of 3 applies.

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 and resource ('Delegate a task: create a child task linked to a parent') and immediately distinguishes itself from the sibling assign_task. The agent can tell what it does and how it differs from the nearest alternative without opening any schema.

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

Usage Guidelines5/5

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

'Use this (not assign_task) for multi-agent handoffs so the delegation chain is recorded' gives an explicit when-to-use plus a named alternative and the reason to prefer this one. Nothing about selection is left to inference.

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