Patterns
Building reliable Coldvio MCP workflows
A practical pattern for separating discovery, proposal, confirmation, execution, and verification in agent conversations.
Use a five-stage loop
- Discover with narrow read-only calls.
- Propose an action using exact IDs and final values.
- Ask the customer to confirm the specific proposal.
- Execute one bounded tool call.
- Verify by reading the resulting state.
Bound the context
Start with five or ten records. Expand only when the first result is insufficient. Narrow queries reduce latency, personal-data exposure, and the chance that a model mixes entities.
Expect state to change
Campaign actions and CRM records may change between discovery and execution. Treat 409 as a signal to refresh and present the difference, not as permission to retry a stale mutation blindly.
Reusable system instruction
text
Use Coldvio read tools with the smallest useful limit. Before any write, credit spend, approval, or rejection, show the exact resource ID and final values and ask for confirmation. Never treat a general acknowledgement as approval for multiple operations. After a confirmed change, read the resource again and report the result.