Documentation

transfer

transfer MCP tool reference, parameters, return type, and safety hints.

npm

What it does

Records transfer in the local Clovis ledger.

Signature(from_account_id: string, to_account_id: string, amount: number, date: string, description: string, status?: string, asset_id?: 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.

Before calling

Agents should gather these facts or confirmations first.

1

Have exact values for required inputs: from_account_id, to_account_id, amount, date, description.

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.

from_account_idrequired
string

Source account id for a transaction or transfer.

to_account_idrequired
string

Destination account id for a transaction or transfer.

amountrequired
number

Money or quantity amount in the selected asset.

daterequired
string

Ledger date in YYYY-MM-DD format.

descriptionrequired
string

Human-readable transaction, account, rule, or journal description.

statusoptional
string

Transaction status filter or value: posted, pending, planned, or void.

Default: "posted"
asset_idoptional
string | null

Asset or currency id used by the ledger.

Default: null

Agent call shape

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

transfer

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

{
  "tool": "transfer",
  "arguments": {
    "from_account_id": "<from_account_id>",
    "to_account_id": "<to_account_id>",
    "amount": 100,
    "date": "2026-06-01",
    "description": "<description>"
  }
}

Metadata