CountBean

generate_report

Convert your Beancount book into a financial report in HTML or XLSX format. Choose HTML for a styled self-contained file, or XLSX with Balance Sheet, Income Statement, and Transactions sheets.

Instructions

Generate a financial report from the book.

format: 'html' (styled, self-contained) or 'xlsx' (Excel workbook with Balance Sheet, Income Statement and Transactions sheets). Returns the path to the written file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generate_report"
  }
}

Input Schema

Name	Required	Description	Default
`as_of`	No
`format`	No		html

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 5, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose output formats, xlsx sheet contents, and the fact that a file path is returned. However, it omits important behavior around the as_of parameter, prerequisites like a connected book, and file lifecycle details such as overwriting or temporary files.

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?

The description is compact and front-loaded, with every sentence contributing useful information. The format block is minimal and scannable, and there is no filler or repetition.

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

Completeness2/5

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

Although the output schema exists and the return path is mentioned, the description is incomplete for invocation because the as_of parameter is unexplained and no preconditions or alternative routing are given. An agent would likely need extra reasoning to use this tool correctly in a nontrivial case.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. The 'format' parameter is well explained with concrete options and sheet contents, but the 'as_of' parameter is completely undocumented, leaving a major semantic gap for a financial report tool.

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

Purpose4/5

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

The description states a clear verb ('Generate') and resource ('financial report from the book'), and adds meaningful detail about supported formats and output. It does not explicitly distinguish itself from sibling tools like balances or assess_book, so it stops short of a 5.

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

Usage Guidelines2/5

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

No guidance is provided about when to choose generate_report over sibling tools such as run_query, balances, or get_ledger. The description explains what the tool does but not the conditions or context that make it the right choice.

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