Documentation

post_journal_entry

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

npm

What it does

Posts journal journal entry in the local Clovis ledger.

Signature(date: string, legs: Array<Record<string, unknown>>, description: string, status?: string, 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: date, legs, 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.

daterequired
string

Ledger date in YYYY-MM-DD format.

legsrequired
object[]

Manual journal legs. Each leg identifies an account and amount.

descriptionrequired
string

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

statusoptional
string

Transaction 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.

post_journal_entry

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

{
  "tool": "post_journal_entry",
  "arguments": {
    "date": "2026-06-01",
    "legs": [],
    "description": "<description>"
  }
}

Metadata