crewchat

hub_task

Coordinate AI coding agent sessions by managing shared tasks: view, add, take, assign, update, lease, return, or park work in one project.

Instructions

Tasks: view, add, take (first wins), assign/areas/park (lead), update, lease, return.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "hub_task"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No	A task: 12 or A12.
`to`	No	assign: the agent.
`live`	No	return: hand over page or device.
`note`	No	update: what happened.
`show`	No	view.	next
`take`	No	add: yours now.
`areas`	No	Path prefixes or globs: app/,*.md.
`files`	No	return: screenshots.
`title`	No	The work; what done looks like.
`where`	No	The machine it needs.
`accept`	No	areas: the suggested.
`action`	Yes	What to do.
`parent`	No	assign title: its task.
`status`	No	update.
`depends`	No	It waits for: A12,A14.
`minutes`	No	lease areas; 0 ends it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv2.0.0Nov 12, 2026

changedInput schema / properties / action / enum

Previous value: -[
-  "view",
-  "add",
-  "take",
-  "assign",
-  "areas",
-  "update"
-]New value: +[
+  "view",
+  "add",
+  "take",
+  "assign",
+  "areas",
+  "update",
+  "lease",
+  "return",
+  "park"
+]

changedInput schema / properties / areas / description

Previous value: -"Path prefixes it changes: app/,docs/."New value: +"Path prefixes or globs: app/,*.md."

changedInput schema / properties / depends / description

Previous value: -"Task numbers it waits for: A12,A14."New value: +"It waits for: A12,A14."

addedInput schema / properties / files

Added value: +{
+  "description": "return: screenshots.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / id / description

Previous value: -"A task number: 12 or A12."New value: +"A task: 12 or A12."

addedInput schema / properties / live

Added value: +{
+  "description": "return: hand over page or device.",
+  "type": "boolean"
+}

addedInput schema / properties / minutes

Added value: +{
+  "description": "lease areas; 0 ends it.",
+  "type": "integer"
+}

changedInput schema / properties / parent / description

Previous value: -"assign title: the task it is part of."New value: +"assign title: its task."

changedInput schema / properties / title / description

Previous value: -"The work, and what done looks like."New value: +"The work; what done looks like."

Addedv1.0.2Oct 22, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare a non-read-only, non-destructive tool. The description adds useful behavior beyond that: take is first-wins, assign/areas/park are lead operations, and lease/return are named, but it omits permissions, reversibility, and detailed lease/return semantics.

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 dense sentence is appropriately front-loaded and free of filler. The parenthetical shorthand is efficient but somewhat cryptic, which keeps it from a 5.

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?

This is a 16-parameter, multi-action tool with no output schema. The description does not explain how to choose among actions, what lease/return entail, or what happens on completion, leaving important context to the schema alone.

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 coverage is 100% and each parameter is documented in the input schema, including enums for action, show, and status. The description mainly restates the action set and adds little parameter meaning beyond the schema, so the baseline of 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?

The one-line description names the resource (tasks) and enumerates supported operations such as view, add, take, assign, update, lease, return, and park, so an agent can identify it as a task-management tool. It does not differentiate from sibling hub_* tools, keeping it below a 5.

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?

It lists actions but gives no explicit when-to-use guidance, prerequisites, or alternatives. Parenthetical hints like '(first wins)' explain behavior rather than action selection, so an agent must infer which action to choose from the schema enums.

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

Deploy Server