agentpack

Overview Schema Source Related Servers Discussions Admin

task_update

Destructive

Patch a Task Passport without changing lifecycle status: append or replace constraints, next actions, tags, and write scope, update repositories, and preserve omitted fields.

Instructions

Patch the current Task Passport without changing lifecycle status. List fields (constraints, writeScope, nextActions, tags) append and deduplicate; repositories upsert by id; omitted fields are preserved; empty or no-op updates fail. Pass clearNextActions to replace the next-actions list instead of appending, e.g. to clear a stale plan before finalizing. Pass replaceConstraints to replace constraints that are obsolete or superseded; removed constraints stay in the task history.

Input Schema

TableJSON Schema

Name	Required	Description
`risk`	No	New risk level for the task.
`tags`	No	Free-form labels to append.
`objective`	No	Replacement objective text.
`writeScope`	No	Repo-relative prefix paths to append to the write scope. A directory path includes its children; globs are not supported.
`constraints`	No	Constraints to append, or the full replacement list when replaceConstraints is true.
`nextActions`	No	Next steps to append, or the full replacement list when clearNextActions is true.
`repositories`	No	Additional checkouts keyed by id; the ledger root is primary. Local updates append scopes; imported bindings use only the supplied local scope. Requires an active task with pending or unknown verification.
`clearNextActions`	No	Replace the next actions with the provided nextActions (or clear them) instead of appending.
`replaceConstraints`	No	Replace the constraints with the provided constraints (or clear them) instead of appending; removed ones are recorded in the task-update event.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.11.0Oct 18, 2026

addedInput schema / properties / repositories

Added value: +{
+  "description": "Additional checkouts keyed by id; the ledger root is primary. Local updates append scopes; imported bindings use only the supplied local scope. Requires an active task with pending or unknown verification.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "description": "Stable unique repository id; primary is reserved.",
+        "type": "string"
+      },
+      "worktree": {
+        "description": "Local Git checkout root, absolute or relative to the pack root.",
+        "type": "string"
+      },
+      "writeScope": {
+        "description": "Non-empty repository-relative prefix paths; dot means the whole checkout.",
+        "items": {
+          "type": "string"
+        },
+        "minItems": 1,
+        "type": "array"
+      }
+    },
+    "required": [
+      "id",
+      "worktree",
+      "writeScope"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed2 schema fields changedv1.9.0Oct 4, 2026

changedInput schema / properties / constraints / description

Previous value: -"Constraints to append."New value: +"Constraints to append, or the full replacement list when replaceConstraints is true."

addedInput schema / properties / replaceConstraints

Added value: +{
+  "description": "Replace the constraints with the provided constraints (or clear them) instead of appending; removed ones are recorded in the task-update event.",
+  "type": "boolean"
+}

Changed7 schema fields changedv1.4.0Jul 10, 2026

addedInput schema / properties / clearNextActions / description

Added value: +"Replace the next actions with the provided nextActions (or clear them) instead of appending."

addedInput schema / properties / constraints / description
```
Added value: +"Constraints to append."
```

addedInput schema / properties / nextActions / description

Added value: +"Next steps to append, or the full replacement list when clearNextActions is true."

addedInput schema / properties / objective / description
```
Added value: +"Replacement objective text."
```
addedInput schema / properties / risk / description
```
Added value: +"New risk level for the task."
```
addedInput schema / properties / tags / description
```
Added value: +"Free-form labels to append."
```

addedInput schema / properties / writeScope / description

Added value: +"Repo-relative prefix paths to append to the write scope. A directory path includes its children; globs are not supported."

First observedv1.3.0Jul 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=true; the description adds the semantics that matter: list fields append and deduplicate, repositories upsert by id, omitted fields are preserved, and empty/no-op updates fail. It also discloses that replaced constraints are retained in task history, which directly qualifies the destructive behavior.

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?

Front-loads purpose and scope in the first sentence, then layers modifier semantics. Dense but every sentence earns its place; slightly heavy parsing load on first read, but no filler.

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?

With no output schema and 9 optional params, the description covers the mutation semantics, preservation behavior, and failure mode (empty/no-op updates fail) that an agent needs. Return-value shape is unspecified, but that gap is minor for a patch tool.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value by explaining how the append-vs-replace flags interact with the list fields and when to prefer replacement. The example ('clear a stale plan before finalizing') gives intent beyond the schema's flat parameter descriptions.

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 ('Patch') and resource ('the current Task Passport') and immediately carves out its boundary: 'without changing lifecycle status'. This lets an agent distinguish it from lifecycle siblings like task_finalize and task_park 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 Guidelines4/5

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

Gives explicit conditional guidance for the two modifier flags, including a concrete scenario ('clear a stale plan before finalizing') and the replacement use case for constraints. It does not name the sibling that handles lifecycle transitions, but the scope boundary plus flag guidance is clear context with no real exclusions left ambiguous.

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

task_update

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools