Validate the outcome
Collect post-run comparison and sign-off evidence instead of treating a completed job as proof that data is correct. Guide-derived workflow; compare with the current six-tool MCP surface.
This is an operational workflow, not an additional callable MCP tool. See the six current tools.
Operator question
Did the intended tables align, and what remains unverified?
The guide calls for evidence before, during and after change, including what was compared and what validation remains.
Context a call would need
- Operation and source/target identities
- Validation scope and criteria
- Approver or reviewer context
Evidence to return
- Compared objects and rows where available
- Differences and unresolved checks
- Review and sign-off record
Safety and availability
The current server has no outcome-validation tool. Generated migration SQL and a completed job are not evidence of matching data; validation remains external to this MCP surface.