Documentation
match_transfers
match_transfers MCP tool reference, parameters, return type, and safety hints.
What it does
Matches transfers in the local Clovis ledger.
(account_a: string, account_b: string, date_tolerance_days?: number, dry_run?: boolean, status?: string) => 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.
Have exact values for required inputs: account_a, account_b.
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.
account_arequiredAccount selected from the local chart of accounts.
account_brequiredAccount selected from the local chart of accounts.
date_tolerance_daysoptionalNumber of days a candidate match may differ by.
Default: 1dry_runoptionalPreview the result without committing changes.
Default: truestatusoptionalTransaction status filter or value: posted, pending, planned, or void.
Default: "pending"Agent call shape
Use the exact tool name and pass arguments as structured JSON through the MCP client.
match_transfers
Copy this shape into agent instructions, evals, or MCP client tests.
{
"tool": "match_transfers",
"arguments": {
"account_a": "<account_a>",
"account_b": "<account_b>",
"dry_run": true
}
}