mcp-agent-hub

dispatch_task

Assign work orders to subagents by creating a task and automatically sending an order message; use parent_id to nest tasks into a hierarchy.

Instructions

主理人专用：向子代理派发任务（工作单）。会创建任务并自动给子代理发一条 order 消息。可传 parent_id 挂到父任务下形成子任务树。

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": {
      "title": "<title>",
      "assignee": "<assignee>"
    },
    "name": "dispatch_task"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No
`agent`	No
`title`	Yes
`assignee`	Yes
`priority`	No
`parent_id`	No
`description`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 27, 2026

TDQS

B3.4/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 meaningfully disclose side effects: it both creates a task and automatically emits an order message to the sub-agent, plus parent_id creates a subtask tree relationship. Still missing are failure behavior for an invalid assignee and any details on the notification's delivery/visibility.

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?

Three short sentences, front-loaded with the access restriction, then the action, then the optional structural parameter. Nothing is padded, though the run-on first clause packs two distinct facts together.

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 side-effect profile is covered. For a 7-parameter mutation tool with 0% schema coverage, though, the description leaves most field-level meaning undocumented, which an agent needs before calling correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, yet only parent_id's semantics are explained (attaching to a parent to form a subtask tree). The most important ambiguity — 'agent' versus 'assignee', and where 'title' vs 'description' boundaries lie — is entirely unaddressed, along with priority scale and tags.

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 and resource ('向子代理派发任务'), and the added clause about auto-sending an order message plus optional parent_id forms a concrete picture of what happens. It is implicitly distinguishable from create_task, but the sibling is never named, so the differentiation is left to inference.

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?

'主理人专用' establishes an authorization precondition and the framing '向子代理派发任务' implies this is for delegating work rather than recording a personal task. However, it never explicitly contrasts dispatch_task with create_task or update_task, so when-not-to-use and alternative selection stay unstated.

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