Documentation

account_register

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

npm

What it does

Shows the transaction register for one account, with date, status, branch, and pagination filters.

Signature(account_id: string, asset_id?: string | null, date_from?: string | null, date_to?: string | null, time_from?: string | null, time_to?: string | null, branch?: string | null, status?: string | null, limit?: number, offset?: number, summary?: boolean) => Record<string, unknown>
read-only

Read-only. This is appropriate for inspection, reporting, diagnostics, and first-pass agent answers.

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 inspect the ledger or answer a question without changing records.
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: account_id.

Parameters

Required inputs are marked clearly. Optional inputs can usually be omitted unless the workflow needs them.

account_idrequired
string

Ledger account id or resolvable account reference.

asset_idoptional
string | null

Asset or currency id used by the ledger.

Default: null
date_fromoptional
string | null

Start date filter in YYYY-MM-DD format.

Default: null
date_tooptional
string | null

End date filter in YYYY-MM-DD format.

Default: null
time_fromoptional
string | null

Start timestamp filter.

Default: null
time_tooptional
string | null

End timestamp filter.

Default: null
branchoptional
string | null

Scenario branch name or id.

Default: null
statusoptional
string | null

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

Default: null
limitoptional
integer

Maximum number of rows to return.

Default: 100
offsetoptional
integer

Number of rows to skip before returning results.

Default: 0
summaryoptional
boolean

Boolean switch for this workflow.

Default: false

Agent call shape

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

account_register

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

{
  "tool": "account_register",
  "arguments": {
    "account_id": "<account_id>"
  }
}

Metadata