Tool reference · Tasks, workflows & decisions
task_create
Starts tracking a task in its first phase (van) and fixes which phases it is allowed to go through.
local stdio server writes
Caution. Each task_id can be created only once; a second call with the same id returns an error.
When to use
- You are beginning a task that you want to move through plan, build and review phases.
- You want phase-specific rules loaded later via self_rules_context.
- You already know the level and want to skip automatic classification.
Parameters
| Name | Type | Default | Description |
|---|---|---|---|
task_idrequired | string | — | — |
descriptionrequired | string | — | — |
level | integer | — | — |
Example
Arguments
{
"task_id": "BILL-142",
"description": "Add rate limiting to the public REST API",
"level": 2
}Result shape
{
"task_id": "BILL-142",
"phase": "van",
"entered_at": "2026-09-25T09:12:04Z",
"level": 2,
"allowed_phases": [
"van",
"plan",
"build",
"reflect",
"archive"
]
}If level is omitted, classify_task picks it. Levels are 1 to 4.
Values are illustrative; the keys follow the server's handler. MCP clients receive the result as JSON text content.
Server description
The description the server sends to your agent in tools/list, captured from the v14.7.0 source:
start a task in `van` phase (auto-classifies level if missing).