# Review a targeted MCP task update

Illustrative planning brief; no automatic product import.

Illustrative case: a user asks to change a task’s priority, but semantic results contain several related tasks.

## Decision

Resolve the exact intended task and field before invoking tb_update_task.

## Owned work

- Verify the target
  - Owner role: Agent
  - Acceptance evidence: The task reference matches the user’s selected work and workspace.
- Bound the requested change
  - Owner role: User
  - Acceptance evidence: The proposed field change contains no extra owner/date/scope edits.
- Check the saved outcome
  - Owner role: Editor
  - Acceptance evidence: The result and later read evidence distinguish requested from applied values.

## Workflow

1. Resolve the target using precise task evidence.
2. Repeat the requested field change without expanding it.
3. Review outcome evidence and reconcile uncertain results before another write.

## Judgment

An MCP update does not inherit the CLI dry-run/apply contract. Do not retry an uncertain write blindly.


## Illustrative update boundary

Target: the user-confirmed task reference.
Requested change: one explicit field.
Excluded: unrequested description, ownership or scheduling edits.
Readback: confirm saved evidence before calling the operation complete.


## Before / after

Before: Update the first related search result and add helpful unrequested edits.

After: Confirm the exact task and requested field; inspect the outcome before reporting completion.


## Workflow questions

### Can a semantic match establish the target?

It can aid discovery, but confirm the exact reference before editing.

### Should an agent also improve the description?

Only when that additional edit is part of the user-approved scope.

## Product connection

Confirm the exact TeamBoost task and permitted change before using the MCP update call, then verify the resulting record.

Confirm account availability before adopting this manual outline.