任务 · 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."

相关