Documentation
match_transfer_pairs
match_transfer_pairs MCP tool reference, parameters, return type, and safety hints.
What it does
Matches transfer pairs in the local Clovis ledger.
(clearing_account?: string | null, account_a?: string | null, account_b?: string | null, date_from?: string | null, date_to?: string | null, date_tolerance_days?: number, match_by?: string, dry_run?: boolean) => Record<string, unknown>Can write, but supports dry-run. Ask the agent to preview the result before committing changes.
When to use it
Use this section to decide whether the tool fits the user request before calling it.
Before calling
Agents should gather these facts or confirmations first.
No required inputs are needed, but date, status, asset, and account filters should still be explicit when the user cares about scope.
Start with dry_run=true, show the preview, then ask before applying the change.
State the intended ledger change in plain language before calling the tool.
Parameters
Required inputs are marked clearly. Optional inputs can usually be omitted unless the workflow needs them.
clearing_accountoptionalAccount selected from the local chart of accounts.
Default: nullaccount_aoptionalAccount selected from the local chart of accounts.
Default: nullaccount_boptionalAccount selected from the local chart of accounts.
Default: nulldate_fromoptionalStart date filter in YYYY-MM-DD format.
Default: nulldate_tooptionalEnd date filter in YYYY-MM-DD format.
Default: nulldate_tolerance_daysoptionalNumber of days a candidate match may differ by.
Default: 0match_byoptionalInput used by this tool.
Default: "amount+date+code"dry_runoptionalPreview the result without committing changes.
Default: trueAgent call shape
Use the exact tool name and pass arguments as structured JSON through the MCP client.
match_transfer_pairs
Copy this shape into agent instructions, evals, or MCP client tests.
{
"tool": "match_transfer_pairs",
"arguments": {
"dry_run": true
}
}