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.

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 supplied, so the description carries the full burden. It only says 'Update a work item' and that the result includes org + bound; it does not disclose permissions, side effects, reversibility, or behavior when only work_id is supplied. This is thin disclosure for a mutating tool.

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?

The description is short and front-loaded, with the core purpose in the first sentence. The second sentence about org + bound is somewhat cryptic and may be redundant given the output schema, so it doesn't fully earn a top score.

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?

For a complex 18-parameter mutation tool with no annotations, this description is under-specified: it lacks usage conditions, exclusions, and side-effect disclosure. The schema covers parameters and output, but the description doesn't complete the behavioral picture an agent needs to choose and invoke the tool safely.

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 baseline is 3. The description's field list is a useful summary but adds little beyond the schema; it does not clarify interactions between assignee_id/assignee_email/assignee_type or due_at/clear_due, which are already documented in the schema.

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?

The description states the action (update), the resource (work item), and examples of mutable fields (status, assignee, priority, parent, due_at). It is clear at a glance, but it doesn't explicitly distinguish this from overlapping siblings such as work_close or work_move, so it stops short of full sibling differentiation.

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 guidance about when to use this tool versus alternatives like work_close, work_move, or work_create, nor any mention of prerequisites or special cases such as clearing fields. The description only states the action and result; an agent must infer the appropriate context from the tool name and sibling names.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.