A court payments agent pulls mixed date formats from clerk and finance MCP tools. How should cross-system formats be normalized?
Select an answer to reveal the explanation.
Short Explanation
Clerk dates and finance dates often disagree on punctuation. Catch them in a PostToolUse hook and normalize once so the payments agent is not juggling two calendars.
Full Explanation
A court payments agent that pulls mixed date formats from clerk and finance MCP tools should normalize those formats in a PostToolUse hook before further model reasoning. Cross-system civic payments depend on comparable due dates, posting dates, and delinquency thresholds; format dialect reconciliation belongs in the pipeline, not in hope.
Keeping both formats side by side and hoping the model reconciles them every turn fails because inconsistent parsing produces intermittent payment-date errors that are hard to audit. Randomly dropping one system's dates to simplify context fails conceptually—it discards evidence needed to reconcile clerk filings with finance postings. Storing dates only as free-text prose without structured normalization fails because prose dates are ambiguous and resist reliable comparison and sorting.
Exam caveat: court calendars and finance ledgers may use different business-day conventions even after string format alignment; normalization should capture calendar rules, not only string shape. Operational check: convert inbound date fields to a canonical ISO datetime with timezone and source system tags in PostToolUse, and add assertions that payment-due comparisons never mix raw Unix and raw locale strings.