タスク · MCP

Complete Task

complete_task is one of the 32 MCP tools in Weft, the AI task manager you run by talking to Claude, Cursor, Codex or ChatGPT through one MCP endpoint. The AI calls this when the work is actually finished — the card moves to Done with completion time recorded, and the optional outcome (what was done, where the result lives) is appended to the card as an "Outcome (AI, date)" note. No column id needed. Work marked as needing you does NOT move to Done: it goes to your queue with the receipt attached, and if the agent said what it would do next, accepting approves exactly that step and hands it back to the agent. If the task carries a verification plan, the server executes its checks right here — fetching the URL, looking for the quote, comparing the hash: an executable/state_delta plan whose blocking checks all pass closes verified by the server; a failed blocking check keeps the card out of Done and shows the agent what the server observed.

Weft は、ひとり創業者と小さなチームのための AI タスク管理です。

ツールリファレンスは英語で管理しています。ツール名、引数、例はどの言語でも同一です。

引数

名前型必須説明
iduuidはいTask id to complete.
outcomestringいいえ1-3 sentences: what was done and where the result lives.
artifacts{ kind, uri }[]いいえEvidence a person could check without trusting the account of it — a URL, a hash, a message id.
learnings(string | { trigger, content })[]いいえUp to 3 lessons worth remembering beyond this task — they become memory notes and surface in every future get_my_work, stamped with source and date.
nextStepstringいいえWhat the agent would do next if you accept (≤200 chars) — shown above the Accept button, so accepting approves exactly that.

戻り値

The task, now in Done with completedAt set — or awaitingReview:true when it stopped at you instead.

注釈

通常の書き込みツールです。状態を変更しますが、ユーザーの意図が分かっていれば MCP クライアントは自由に呼び出せます。確認を求めるかどうかはクライアント次第です。Model Context Protocol の仕様は、ツールの呼び出しを拒否できる形で人間が関与し続けることを推奨しています。

例

ユーザーの発言:

"Mark the deploy task done — released in v1.2.0."

関連