Cofounder
What exactly did the user approve when the agent clicked Send?
A small tool-contract exercise for developers building review and confirmation into an agent workflow.
“Send the update to the client” sounds precise until you build the review screen. Which draft? Which recipient? What if someone changes the address after the person presses Approve? A green confirmation button is only as meaningful as the information it covers.
The MCP tools specification describes how servers expose named tools with input schemas. Anthropic’s account of Claude Duet gives a concrete interface example: for certain sensitive actions it presents the action, destination and content for review. Use those references to design a contract for a fictional project-update tool. Model Context Protocol • Tools Anthropic • Approval design in Claude Duet
Make an approval refer to a particular draft
Start with a draft containing a recipient, subject, body, attachment list and version. Show the fields that determine what leaves the workspace. When the user approves, record that version. If a teammate changes the recipient or adds an attachment, present the revised draft for a new decision. A recipient’s display name alone is a poor identifier when two client contacts share a name.
| Review case | Expected result |
|---|---|
| Approved draft stays the same | The sent receipt identifies the reviewed version and recipient. |
| Attachment changes after approval | The revised version returns to review. |
| A second click arrives during delivery | The interface shows the existing operation and its status. |
| Delivery status is uncertain | The interface checks the existing receipt before offering another send. |
Try the four cases with an in-memory outbox and invented addresses. Check the outbox after each case. A transcript in which the assistant says “I sent it” is easy to produce. An outbox entry tied to the approved version is evidence the implementation did the right thing.