journalize

get_income_statement

Income statement, period-scoped by since/until (ISO date strings, both optional — omitted means whole history). Always books full history first, then clamps the output to the requested period (never filters input dates — see reports.py for why). Shares a combined free allowance of 2 with export_ledger, get_balance_sheet, and get_trial_balance (the "report tier") — not 2 free calls each.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`nonce`	Yes
`since`	No
`until`	No
`signature`	Yes
`timestamp`	Yes
`public_key`	Yes
`payment_header`	No

TDQS

A4.2/5.0

Behavior5/5

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

With no annotations, the description fully carries the burden, revealing that the tool books full history then clamps output, and shares a combined allowance with three sibling tools.

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

Conciseness4/5

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

Two sentences with no wasted words, but the second sentence is dense and could be broken for readability.

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

Completeness3/5

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

Covers purpose, key params, and behavioral quirk, but lacks description of return format (no output schema) and does not explain auth parameters, leaving some gaps.

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

Parameters3/5

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

The description adds meaning for 'since' and 'until' (ISO dates, optional, behavior when omitted) but ignores the five other parameters (auth fields, payment_header), and schema coverage is 0%.

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?

The description clearly states it produces an income statement, period-scoped by since/until, and differentiates from sibling tools by mentioning combined allowance with report-tier siblings.

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?

The description specifies when to use (for income statements) and notes shared allowance with related tools, but does not explicitly state when not to use or name alternatives.

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

All journalize tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: account inquiries, financial reports, directive management, validation, key generation, and batch submission. No two tools overlap in functionality despite some being related reports.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., export_ledger, get_balance_sheet, list_accounts). The naming is predictable and clear throughout.

Tool Count5/5

With 11 tools covering ledger management, reporting, validation, and key generation, the count is well-scoped for the server's purpose. Each tool justifies its existence without being too few or too many.

Completeness5/5

The tool set covers essential operations for a Beancount ledger: submission of directives (single and batch), listing of accounts and directives, generation of key financial reports, balance queries, validation, and key registration. No obvious gaps are present.

Resources

Need Help?