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 este managerul de sarcini cu AI pentru fondatori solo și echipe mici.
Referința instrumentelor este întreținută în engleză: numele instrumentelor, argumentele și exemplele sunt identice în toate limbile.
Argumente
| Nume | Tip | Obligatoriu | Descriere |
|---|---|---|---|
| id | uuid | da | Task id to complete. |
| outcome | string | nu | 1-3 sentences: what was done and where the result lives. |
| artifacts | { kind, uri }[] | nu | Evidence a person could check without trusting the account of it — a URL, a hash, a message id. |
| learnings | (string | { trigger, content })[] | nu | 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. |
| nextStep | string | nu | What the agent would do next if you accept (≤200 chars) — shown above the Accept button, so accepting approves exactly that. |
Returnează
The task, now in Done with completedAt set — or awaitingReview:true when it stopped at you instead.
Adnotări
Instrument de scriere implicit. Instrumentul modifică starea; clienții MCP îl pot apela liber odată ce știu ce vrea utilizatorul. Dacă clientul cere confirmare este alegerea clientului; specificația Model Context Protocol recomandă păstrarea unui om în buclă, cu posibilitatea de a refuza apelurile de instrumente.
Exemplu
Ce spune utilizatorul:
"Mark the deploy task done — released in v1.2.0."Vezi și
- Toate cele 32 de instrumente MCP — vederea de catalog.
- Suveica — cum folosește clientul AI aceste instrumente.
- Apelează acest instrument prin propriul tău client: vezi ghidurile de configurare sau accesează direct
https://letsweft.com/api/mcp.