classify_task

When to use

• At the start of a task, to decide how much planning it deserves.
• You want a rough token budget before committing to an approach.
• You are about to call task_create and want to see the level it would pick.

Parameters

Name	Type	Default	Description
descriptionrequired	string	—	—
project	string	—	—

Example

Arguments

{
  "description": "Add rate limiting to the public REST API",
  "project": "billing-api"
}

Result shape

{
  "level": 2,
  "suggested_phases": [
    "van",
    "plan",
    "build",
    "reflect",
    "archive"
  ],
  "estimated_tokens": 8000,
  "rationale": "fallback by length (2) — no keyword match; 2 analogous past items (avg 0.41)",
  "confidence": 0.7,
  "analogy": {
    "count": 2,
    "avg_score": 0.41
  }
}

Rule-based: keyword matches give confidence 1.0, otherwise the level is guessed from description length. No LLM is called.

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:

classify task into L1-L4 complexity + suggested phases.

Related tools

• task_create
• workflow_predict
• analogize