complete-task

Explicit task completion requires calling complete_task with a status (success, blocked, or partial), original request summary, and work summary. This enforces a formal signal so tasks don't remain ambiguous or unfinished, enabling reliable downstream automation.

Task completion supports three statuses: success for fully completed work, blocked when work cannot proceed, and partial for incomplete progress. Each status preserves the original request context and requires a concise summary of what was accomplished.

Yes, the complete_task tool includes an optional remaining_work field to document what still needs completion. This enables clear handoffs and helps downstream processes understand what blocked or partial tasks require next.

Task completion runs natively within the MCP runtime without external installations or dependencies. The complete_task tool is available immediately for structuring task endpoints across all lifecycle stages.

Complete_task captures the original_request_summary to preserve what was initially asked, alongside a summary of what was done. This context retention ensures reviewers and downstream automation understand intent and outcomes.