TeamShared

work_list

List org work items (shared task queue for humans and agents).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tag`	No	Only items carrying this label
`mine`	No	Only items assigned to the caller (human or agent)
`sort`	No	Sort key	updated_at
`limit`	No
`offset`	No	Pagination offset
`has_due`	No	True: only dated items; False: only undated
`assignee`	No	Filter by user email, agent name, actor id, or 'unassigned'. Names that match nobody return no items
`due_from`	No	Inclusive start of due_at window (UTC)
`sort_dir`	No	asc or desc	desc
`due_until`	No	Exclusive end of due_at window (UTC)
`item_type`	No	Filter: task, milestone, or approval
`project_id`	No	Filter to work linked to this project UUID
`work_status`	No	Filter by workflow status
`closed_since`	No	Also include items closed at or after this instant (UTC)
`initiative_id`	No	Filter to tasks linked to a strategic initiative UUID
`work_statuses`	No	Match any of these statuses (e.g. todo, in_progress, blocked)
`exclude_closed`	No	Omit done/cancelled items (default true)
`include_cancelled`	No	False drops cancelled items (default true)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields 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"
+  }
+]

changedInput schema / properties / work_statuses / anyOf

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

Changed6 schema fields changedSep 27, 2026

changedInput schema / properties / assignee / description

Previous value: -"Filter by agent name or user email"New value: +"Filter by user email, agent name, actor id, or 'unassigned'. Names that match nobody return no items"

addedInput schema / properties / closed_since

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Also include items closed at or after this instant (UTC)"
+}

addedInput schema / properties / include_cancelled

Added value: +{
+  "default": true,
+  "description": "False drops cancelled items (default true)",
+  "type": "boolean"
+}

changedInput schema / properties / sort / enum

Previous value: -[
-  "updated_at",
-  "priority",
-  "work_status",
-  "created_at"
-]New value: +[
+  "updated_at",
+  "priority",
+  "work_status",
+  "created_at",
+  "due_at"
+]

addedInput schema / properties / tag

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only items carrying this label"
+}

addedInput schema / properties / work_statuses

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "enum": [
+          "backlog",
+          "todo",
+          "in_progress",
+          "blocked",
+          "done",
+          "cancelled"
+        ],
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Match any of these statuses (e.g. todo, in_progress, blocked)"
+}

Changed5 schema fields changedSep 7, 2026

addedInput schema / properties / due_from

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Inclusive start of due_at window (UTC)"
+}

addedInput schema / properties / due_until

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Exclusive end of due_at window (UTC)"
+}

addedInput schema / properties / has_due

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "True: only dated items; False: only undated"
+}

addedInput schema / properties / item_type

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "task",
+        "milestone",
+        "approval"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter: task, milestone, or approval"
+}

addedInput schema / properties / project_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Filter to work linked to this project UUID"
+}

First observedAug 18, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only says 'List.' It never discloses the non-obvious defaults that materially change results (exclude_closed=true, include_cancelled=true, limit=50/max 200). The read-only nature is only implied by 'List,' and no auth or scoping behavior is described.

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?

A single front-loaded sentence with zero waste. It is appropriately terse, though the extreme brevity leaves the heavy 18-parameter surface entirely to the schema.

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 no explanation, and the schema covers the parameters well. But for a list tool with 18 filters and surprising defaults, the one-line description is thin and leaves the agent relying entirely on structured fields.

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 94%, so the schema already documents nearly all 18 parameters including enum values and defaults. The description adds no parameter meaning beyond what the schema provides, so the baseline 3 applies.

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 (List) and resource (org work items), plus a clarifying parenthetical that this is a shared task queue for humans and agents. It cleanly separates from the singular work_get, but does not explicitly differentiate from other listers like work_comment_list or project_list.

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 guidance, no prerequisites, and no alternatives named. The parenthetical adds domain context but not selection criteria; an agent gets no signal on when this list is preferable to work_get or the other list tools.

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.