Beancount.io

Append Beancount Directive Text

appendLedgerText

Append Beancount directive text as you would write it into a file; postings indented under their transaction. Routes each directive to its file by type and date (path overrides) and inserts it in date order. Max 50 directives. Non-directive text, and text introducing new bean-check errors (UNBALANCED when a transaction does not balance), are refused unless allowInvalid. dry_run returns the diff and projected errors without committing. Adds directives without rewriting files, unlike updateLedgerFiles. The commit message is composed from the appended text; there is no message argument. Syntax: https://beancount.github.io/docs/beancount_language_syntax/

Input Schema

Name	Required	Description
`path`	No	Target file; omit to auto-route.
`text`	Yes	e.g. `2026-01-02 * "Cafe" ""` plus indented postings.
`dryRun`	No	Alias of dry_run, as REST and GraphQL spell it.
`ledger`	No	Target ledger as owner/name. Required for an unpinned credential; defaults to the credential's ledger restriction.
`dry_run`	No
`allowInvalid`	No
`allow_invalid`	No	Alias of allowInvalid.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`result`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026

removedInput schema / properties / allowInvalid / default
```
Removed value: -false
```

addedInput schema / properties / allow_invalid

Added value: +{
+  "description": "Alias of allowInvalid.",
+  "type": "boolean"
+}

addedInput schema / properties / dryRun

Added value: +{
+  "description": "Alias of dry_run, as REST and GraphQL spell it.",
+  "type": "boolean"
+}

removedInput schema / properties / dry_run / default
```
Removed value: -false
```

First observedOct 24, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial behavior beyond annotations: max 50 directives, routing by type and date with path overrides, rejection of non-directive text and new bean-check errors unless allowInvalid, and dry_run producing diff/errors without committing. It also notes that commit messages are composed automatically, so there is no message argument.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action, then covers routing, limits, validation, dry-run behavior, sibling contrast, and commit-message behavior in dense but efficient sentences. The syntax link is appropriately placed at the end.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a mutation tool with annotations and an output schema: it explains validation, routing, limits, dry-run behavior, and key parameter effects. Return-value details are not required because an output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds clear meaning for key parameters: text is Beancount directive syntax with indented postings, path overrides automatic routing, dry_run returns a diff and projected errors, and allowInvalid permits invalid content. Schema coverage is 71%, and the description supplies the most important semantic context beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: appending Beancount directive text as file content, with postings indented. It also distinguishes itself from updateLedgerFiles, making the scope clear enough to select without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the main usage context, routing/date-order behavior, the 50-directive limit, refusal conditions, and explicitly contrasts with updateLedgerFiles. It does not address when to choose addLedgerEntries instead, so it stops short of fully exhaustive sibling guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Beancount.io tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.