request_planning
Register user requests and plan associated tasks to initiate structured workflows within the MCP TaskManager server.
Instructions
Register a new user request and plan its associated tasks. You must provide 'originalRequest' and 'tasks', and optionally 'splitDetails'.
This tool initiates a new workflow for handling a user's request. The workflow is as follows:
Use 'request_planning' to register a request and its tasks.
After adding tasks, you MUST use 'get_next_task' to retrieve the first task. A progress table will be displayed.
Use 'get_next_task' to retrieve the next uncompleted task.
IMPORTANT: After marking a task as done, the assistant MUST NOT proceed to another task without the user's approval. The user must explicitly approve the completed task using 'approve_task_completion'. A progress table will be displayed before each approval request.
Once a task is approved, you can proceed to 'get_next_task' again to fetch the next pending task.
Repeat this cycle until all tasks are done.
After all tasks are completed (and approved), 'get_next_task' will indicate that all tasks are done and that the request awaits approval for full completion.
The user must then approve the entire request's completion using 'approve_request_completion'. If the user does not approve and wants more tasks, you can again use 'request_planning' to add new tasks and continue the cycle.
The critical point is to always wait for user approval after completing each task and after all tasks are done, wait for request completion approval. Do not proceed automatically.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| originalRequest | Yes | ||
| splitDetails | No | ||
| tasks | Yes |
Implementation Reference
- index.ts:323-357 (handler)The core handler function for the 'request_planning' tool. It increments counters to generate unique IDs for the request and tasks, constructs Task objects from input, adds the new RequestEntry to the data store, saves to persistent storage, and returns the requestId and a progress table message.
public async requestPlanning( originalRequest: string, tasks: { title: string; description: string }[], splitDetails?: string ) { this.requestCounter++; const requestId = `req-${this.requestCounter}`; const taskEntries: Task[] = tasks.map((t) => { this.taskCounter++; return { id: `task-${this.taskCounter}`, title: t.title, description: t.description, done: false, approved: false, completedDetails: "", }; }); this.data.requests.push({ requestId, originalRequest, splitDetails: splitDetails || "", tasks: taskEntries, completed: false, }); await this.saveTasks(); return { requestId, message: "Request registered successfully.\n" + this.formatTaskProgressTable(requestId), }; } - index.ts:32-41 (schema)Zod schema defining the input structure for the request_planning tool: originalRequest, optional splitDetails, and array of tasks with title and description.
const RequestPlanningSchema = z.object({ originalRequest: z.string(), splitDetails: z.string().optional(), tasks: z.array( z.object({ title: z.string(), description: z.string(), }) ), }); - index.ts:145-149 (registration)Registers the request_planning tool within the listTools() method of the TaskManagerServer class, specifying its name, description, and input schema.
{ name: "request_planning", description: "Register a new user request and plan its associated tasks.", inputSchema: RequestPlanningSchema, },