infer_task_progress

Analyze code changes and file activity in a directory to infer task completion status, enabling automated progress tracking for software projects. Supports customizable file extensions, scan depth, and confidence thresholds.

Instructions

Analyze the codebase to infer which tasks appear to be completed based on code changes, file creation, and implementation evidence. Intelligent progress inference to automatically track task completion from code analysis.

Input Schema

Name	Required	Description
`autoUpdateTasks`	No	Whether to automatically update task status based on inference
`confidenceThreshold`	No	Confidence threshold for auto-updating tasks (0-1)
`fileExtensions`	No	File extensions to analyze
`projectId`	No	Filter analysis to a specific project
`scanDepth`	No	Directory depth to scan for code files
`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": {
    "autoUpdateTasks": {
      "default": false,
      "description": "Whether to automatically update task status based on inference",
      "type": "boolean"
    },
    "confidenceThreshold": {
      "default": 0.7,
      "description": "Confidence threshold for auto-updating tasks (0-1)",
      "maximum": 1,
      "minimum": 0,
      "type": "number"
    },
    "fileExtensions": {
      "default": [
        ".js",
        ".ts",
        ".jsx",
        ".tsx",
        ".py",
        ".java",
        ".cs",
        ".go",
        ".rs"
      ],
      "description": "File extensions to analyze",
      "items": {
        "type": "string"
      },
      "type": "array"
    },
    "projectId": {
      "description": "Filter analysis to a specific project",
      "type": "string"
    },
    "scanDepth": {
      "default": 3,
      "description": "Directory depth to scan for code files",
      "maximum": 5,
      "minimum": 1,
      "type": "number"
    },
    "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

infer_task_progress

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from Agentic Tools MCP Server

Related Tools

MCP directory API