recategorize_transaction

What it does

Recategorizes transaction in the local Clovis ledger.

Signature

(tx_id: string, new_account_id: string, old_account_id?: string | null, correction_date?: string | null, dry_run?: boolean) => Record<string, unknown>

can writedry-run

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.

Use it when an agent needs to prepare a change and show a preview before committing it.

Use it when working with accounts, transactions, balances, registers, or double-entry records.

Before calling

Agents should gather these facts or confirmations first.

1

Have exact values for required inputs: tx_id, new_account_id.

2

Start with dry_run=true, show the preview, then ask before applying the change.

3

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.

tx_idrequired

string

Transaction id.

new_account_idrequired

string

Identifier from the local Clovis ledger.

old_account_idoptional

string | null

Identifier from the local Clovis ledger.

Default: null

correction_dateoptional

string | null

Date value, usually in YYYY-MM-DD format.

Default: null

dry_runoptional

boolean

Preview the result without committing changes.

Default: false

Agent call shape

Use the exact tool name and pass arguments as structured JSON through the MCP client.

Copy this shape into agent instructions, evals, or MCP client tests.

{
  "tool": "recategorize_transaction",
  "arguments": {
    "tx_id": "<tx_id>",
    "new_account_id": "<new_account_id>",
    "dry_run": true
  }
}

Metadata

CategoryLedger and accounts

ReturnsobjectReturns object from the local ledger.

AliasesNone