AI Team OS

by CronusL-1141

Overview Schema Source Related Servers Discussions Admin

Python

Local

task_update

Update task fields; omitted values stay unchanged, empty text clears.

Instructions

Update task fields; omitted values stay unchanged, empty text clears.

Completion shares the HTTP complete path's validation and dependency unlock.

Input Schema

Name	Required	Description	Default
`tags`	No	Tag list; [] clears it
`title`	No	New non-empty title; omitted keeps it
`fields`	No	"all" (default, compatible) / "compact" write receipt	all
`result`	No	Result text; empty string clears it
`status`	No	pending/blocked/running/completed/failed; blocked explicitly means manual
`horizon`	No	short/mid/long
`task_id`	Yes	Task ID
`priority`	No	critical/high/medium/low
`parent_id`	No	Same-project parent ID; empty string detaches, omitted keeps it
`depends_on`	No	Same-project dependency IDs; [] clears, omitted keeps
`waiting_on`	No	kind=user/agent, target_id and reason; {} clears waiting
`assigned_to`	No	Agent name/ID; empty string clears assignment
`description`	No	Description; empty string clears it
`status_note`	No	Current status explanation; empty string clears
`expected_revision`	No	Revision observed before editing; mismatches return conflict

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed33 schema fields changedv1.15.2Oct 14, 2026

addedInput schema / properties / assigned_to / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / assigned_to / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / assigned_to / description

Previous value: -"Agent name or ID to assign the task to"New value: +"Agent name/ID; empty string clears assignment"

removedInput schema / properties / assigned_to / type
```
Removed value: -"string"
```

addedInput schema / properties / depends_on

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Same-project dependency IDs; [] clears, omitted keeps"
+}

addedInput schema / properties / description / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / description / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / description / description

Previous value: -"New task description"New value: +"Description; empty string clears it"

removedInput schema / properties / description / type
```
Removed value: -"string"
```

addedInput schema / properties / expected_revision

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Revision observed before editing; mismatches return conflict"
+}

addedInput schema / properties / fields

Added value: +{
+  "default": "all",
+  "description": "\"all\" (default, compatible) / \"compact\" write receipt",
+  "type": "string"
+}

addedInput schema / properties / horizon

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "short/mid/long"
+}

addedInput schema / properties / parent_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Same-project parent ID; empty string detaches, omitted keeps it"
+}

addedInput schema / properties / priority / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / priority / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / priority / description

Previous value: -"Priority: critical / high / medium / low"New value: +"critical/high/medium/low"

removedInput schema / properties / priority / type
```
Removed value: -"string"
```

addedInput schema / properties / result / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / result / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / result / description

Previous value: -"Task result text (typically filled when completing)"New value: +"Result text; empty string clears it"

removedInput schema / properties / result / type
```
Removed value: -"string"
```

addedInput schema / properties / status / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / status / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / status / description

Previous value: -"New status: pending / blocked / running / completed / failed"New value: +"pending/blocked/running/completed/failed; blocked explicitly means manual"

removedInput schema / properties / status / type
```
Removed value: -"string"
```

addedInput schema / properties / status_note

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Current status explanation; empty string clears"
+}

changedInput schema / properties / tags / description

Previous value: -"New tag list (replaces existing tags)"New value: +"Tag list; [] clears it"

changedInput schema / properties / task_id / description

Previous value: -"Task ID (required)"New value: +"Task ID"

addedInput schema / properties / title / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / title / default
```
Previous value: -""New value: +null
```

changedInput schema / properties / title / description

Previous value: -"New task title"New value: +"New non-empty title; omitted keeps it"

removedInput schema / properties / title / type
```
Removed value: -"string"
```

addedInput schema / properties / waiting_on

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "kind=user/agent, target_id and reason; {} clears waiting"
+}

First observedv1.9.0Jul 14, 2026

TDQS

B3.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 disclose non-obvious mutation behavior: omitted values are preserved, empty text clears fields, and marking completion triggers the same validation and dependency-unlock path as HTTP complete. It stops short of permissions, reversibility, and error semantics.

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

Conciseness4/5

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

Two tight sentences with no waste, and the core partial-update rule is front-loaded. The second sentence is somewhat jargon-heavy ('HTTP complete path') but still earns its place by flagging a side effect.

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 15-parameter mutation tool with no annotations, the description covers update semantics and one side effect, and the output schema handles return values. However, it omits auth/permission needs and reversibility, which a mutation tool with zero annotation coverage should ideally state.

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 each parameter's semantics (clear/keep via empty string/omission, enum-like value lists, conflict on expected_revision) are already documented in the schema. The description only generalizes this rule and adds no per-parameter detail beyond it, matching the baseline for fully-covered schemas.

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 specific verb+resource ('Update task fields') and immediately clarifies the partial-update semantics. An agent can tell it apart from task_create/task_status by the verb, but the description never names or contrasts a sibling explicitly.

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?

No when-to-use or when-not guidance, and no routing against siblings like task_create, task_status, or task_run. The brief mention of the 'complete path' hints at a completion use-case but does not frame it as a condition for selecting this tool.

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

Deploy Server