TeamShared

work_create

Create a work item. Created active immediately for humans and agents (no approval queue).

Creating-agent path: omitted priority → skill task-priority-assessment; omitted due_at → skill task-time-required. The distiller does not fill these. Console blanks default to priority=normal only. Result includes org + bound.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`repo`	No	Optional workspace slug tag
`tags`	No	Optional tags
`agent`	No	Override agent identity
`title`	Yes	Short task title
`due_at`	No	Optional due datetime. If omitted, fetch skill task-time-required and pass the computed due_at
`github`	No	Optional owner/repo tag
`part_of`	No	Ontology entity this beat belongs to (campaign Project name)
`priority`	No	urgent, high, normal, low. If the user/packet did not name one, fetch skill task-priority-assessment first — do not silently take the normal default	normal
`start_at`	No	Optional start datetime
`item_type`	No	task, milestone, or approval	task
`parent_id`	No	Parent task UUID (makes this a subtask)
`project_id`	No	Add the task to this project UUID
`section_id`	No	Place in this project section UUID
`assignee_id`	No	Assignee UUID
`description`	No	Alias for description_md
`work_status`	No	Initial workflow status	todo
`assignee_type`	No	Assignee type (user)
`initiative_id`	No	Optional strategic initiative UUID
`playbook_slug`	No	Named playbook to inject when agent_run_start(work_id=) spawns (e.g. teamshared-manager). Unset = no inject
`assignee_email`	No	Assign to org member by email
`description_md`	No	Optional markdown body
`assigned_to_entity`	No	Ontology Person or Agent name (graph assigned_to; not assignee_email)

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 / enum

Previous value: -[
-  "backlog",
-  "todo",
-  "in_progress",
-  "blocked",
-  "done",
-  "cancelled"
-]New value: +[
+  "backlog",
+  "todo",
+  "in_progress",
+  "in_review",
+  "blocked",
+  "done",
+  "cancelled"
+]

Changed2 schema fields changedSep 7, 2026

changedInput schema / properties / due_at / description

Previous value: -"Optional due datetime"New value: +"Optional due datetime. If omitted, fetch skill task-time-required and pass the computed due_at"

changedInput schema / properties / priority / description

Previous value: -"urgent, high, normal, low"New value: +"urgent, high, normal, low. If the user/packet did not name one, fetch skill task-priority-assessment first — do not silently take the normal default"

Changed1 schema field changedSep 1, 2026

addedInput schema / properties / playbook_slug

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Named playbook to inject when agent_run_start(work_id=) spawns (e.g. teamshared-manager). Unset = no inject"
+}

Changed2 schema fields changedAug 30, 2026

addedInput schema / properties / assigned_to_entity

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Ontology Person or Agent name (graph assigned_to; not assignee_email)"
+}

addedInput schema / properties / part_of

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Ontology entity this beat belongs to (campaign Project name)"
+}

First observedAug 18, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: the item is active immediately with no approval queue, the distiller will not auto-fill omitted priority/due_at, and console blanks default only to priority=normal. It omits permissions/auth requirements and any notification side effects, keeping it short of a 5.

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 the core purpose in the first sentence and is compact for a 22-parameter tool. The multi-line 'Creating-agent path' block is efficient, though the stray markdown around ``org`` + ``bound`` is slightly rough.

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?

For a 22-param creation tool with an output schema (so return values need no explanation) and no annotations, the description covers the critical behavioral nuances an agent needs: activation, no approval queue, and skill fallbacks for omitted fields. The unmentioned optional parameters are adequately covered by the 100%-coverage schema.

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% and the param descriptions already instruct fetching the priority/time skills, so the schema does the heavy lifting. The description adds a small nuance about distiller and console default behavior, but does not materially explain the many optional parameters (project_id, section_id, assignee_*, etc.).

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+resource ('Create a work item') and immediately clarifies the activation semantics ('created active immediately... no approval queue'). It distinguishes the resource from siblings like work_update, work_close, and project_create, though it never names an alternative tool explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Provides procedural guidance for the creating-agent path (omitted priority → skill task-priority-assessment; omitted due_at → skill task-time-required), which is useful. However, it gives no when-to-use/when-not-to-use routing versus sibling tools such as project_create or process_run_create, leaving tool selection to inference.

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.