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.

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

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'List', implying a read operation, but does not mention pagination behavior, default filters (e.g., exclude_closed defaults true), or any potential side effects. The shared queue context is mentioned but not elaborated.

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

Conciseness5/5

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

A single sentence with no filler, front-loading the core purpose. It is highly concise and immediately clear.

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?

The output schema exists and parameter descriptions are detailed, so much of the contextual burden is handled. However, the description does not mention that this is a shared queue for humans and agents beyond a parenthetical, nor does it explain any unique behaviors like default filtering. For a tool with 18 parameters, a bit more context would help but is not critical given the schema richness.

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 most parameters are already well documented in the input schema. The description adds no additional meaning or context for parameters. Baseline 3 is appropriate because the schema carries the heavy lifting.

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?

The description clearly states the verb 'List' and the resource 'org work items', and adds context that this is a 'shared task queue for humans and agents'. This distinguishes it from single-item tools like work_get and create tools like work_create without ambiguity.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention work_get for single items, work_create for creating, or other list tools. There is no explicit context for when this is the appropriate choice.

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.