analyze_task_complexity

Assess task complexity and recommend breaking down complex tasks into simpler subtasks for improved productivity and progress tracking. Specify thresholds to automate task division when needed.

Instructions

Analyze task complexity and suggest breaking down overly complex tasks into smaller, manageable subtasks. Intelligent complexity analysis to identify tasks that should be split for better productivity and progress tracking.

Input Schema

Name	Required	Description
`autoCreateSubtasks`	No	Whether to automatically create suggested subtasks
`complexityThreshold`	No	Complexity threshold above which tasks should be broken down
`projectId`	No	Filter analysis to a specific project
`suggestBreakdown`	No	Whether to suggest specific task breakdowns
`taskId`	No	Specific task ID to analyze (if not provided, analyzes all tasks)
`workingDirectory`	Yes	The full absolute path to the working directory where data is stored. MUST be an absolute path, never relative. Windows: "C:\Users\username\project" or "D:\projects\my-app". Unix/Linux/macOS: "/home/username/project" or "/Users/username/project". Do NOT use: ".", "..", "~", "./folder", "../folder" or any relative paths. Ensure the path exists and is accessible before calling this tool. NOTE: When server is started with --claude flag, this parameter is ignored and a global user directory is used instead.

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "autoCreateSubtasks": {
      "default": false,
      "description": "Whether to automatically create suggested subtasks",
      "type": "boolean"
    },
    "complexityThreshold": {
      "default": 7,
      "description": "Complexity threshold above which tasks should be broken down",
      "maximum": 10,
      "minimum": 1,
      "type": "number"
    },
    "projectId": {
      "description": "Filter analysis to a specific project",
      "type": "string"
    },
    "suggestBreakdown": {
      "default": true,
      "description": "Whether to suggest specific task breakdowns",
      "type": "boolean"
    },
    "taskId": {
      "description": "Specific task ID to analyze (if not provided, analyzes all tasks)",
      "type": "string"
    },
    "workingDirectory": {
      "description": "The full absolute path to the working directory where data is stored. MUST be an absolute path, never relative. Windows: \"C:\\Users\\username\\project\" or \"D:\\projects\\my-app\". Unix/Linux/macOS: \"/home/username/project\" or \"/Users/username/project\". Do NOT use: \".\", \"..\", \"~\", \"./folder\", \"../folder\" or any relative paths. Ensure the path exists and is accessible before calling this tool. NOTE: When server is started with --claude flag, this parameter is ignored and a global user directory is used instead.",
      "type": "string"
    }
  },
  "required": [
    "workingDirectory"
  ],
  "type": "object"
}

Agentic Tools MCP Server

analyze_task_complexity

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from Agentic Tools MCP Server

Related Tools

MCP directory API