TeamShared

work_update

Update a work item (status, assignee, priority, parent, due_at, etc.).

Result includes org + bound.

Input Schema

TableJSON Schema

Name	Required	Description
`repo`	No	Workspace slug tag
`tags`	No	Replace tags
`agent`	No	Override agent identity
`title`	No	New title
`due_at`	No	Due datetime. Omit to leave unchanged; use clear_due to unset
`github`	No	owner/repo tag
`work_id`	Yes	Work item UUID
`priority`	No	urgent, high, normal, low
`clear_due`	No	Clear due_at. Omit due_at to leave the date unchanged
`parent_id`	No	Parent task UUID (reparent as subtask)
`assignee_id`	No	Assignee UUID
`work_status`	No	Workflow status
`assignee_type`	No	Assignee type (user)
`initiative_id`	No	Strategic initiative UUID
`playbook_slug`	No	Named playbook injected on agent_run_start(work_id=). Empty string clears. Omit to leave unchanged
`assignee_email`	No	Assign to user by email
`blocked_reason`	No	Why blocked (when status=blocked)
`description_md`	No	New markdown body

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedInput schema / properties / work_status / anyOf

Previous value: -[
-  {
-    "enum": [
-      "backlog",
-      "todo",
-      "in_progress",
-      "blocked",
-      "done",
-      "cancelled"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "backlog",
+      "todo",
+      "in_progress",
+      "in_review",
+      "blocked",
+      "done",
+      "cancelled"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

Changed4 schema fields changedSep 10, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "anyOf": [
-      {
-        "additionalProperties": true,
-        "type": "object"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

Changed2 schema fields changedSep 7, 2026

addedInput schema / properties / clear_due

Added value: +{
+  "default": false,
+  "description": "Clear due_at. Omit due_at to leave the date unchanged",
+  "type": "boolean"
+}

changedInput schema / properties / due_at / description

Previous value: -"Due datetime"New value: +"Due datetime. Omit to leave unchanged; use clear_due to unset"

Changed1 schema field changedSep 1, 2026

addedInput schema / properties / playbook_slug

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Named playbook injected on agent_run_start(work_id=). Empty string clears. Omit to leave unchanged"
+}

First observedAug 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a mutation with 18 parameters. It says nothing about partial-update semantics, required permissions, irreversibility, or empty-string/clear conventions; the only disclosure is a cryptic 'Result includes ``org`` + ``bound``' that is not explained.

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 short sentences, front-loaded with the action and affected fields. The trailing 'Result includes ``org`` + ``bound``' sentence is terse but cryptic and largely redundant given the output schema exists.

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?

An output schema exists, so return values need not be described, and the schema fully documents the 18 parameters. However, a no-annotation mutation tool with reparenting, status transitions, and field-clearing behavior should at minimum signal update semantics or routing to work_move/work_close.

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 every parameter, including the important 'Omit to leave unchanged' and 'use clear_due to unset' semantics. The description's field list merely mirrors the schema, so the baseline 3 is appropriate.

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 and resource ('Update a work item') and enumerates representative updatable fields (status, assignee, priority, parent, due_at). It does not distinguish itself from near-siblings like work_move (parent/project changes) or work_close (terminal status), but the core purpose is unambiguous.

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 at all. For a tool whose field list overlaps work_move (parent_id), work_close (work_status=done/cancelled), and work_add_to_project (initiative/project), the description never says which sibling to prefer or under what conditions.

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

All TeamShared tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.