Caribooks (QuickBooks Online)

get balance sheet detail

get_balance_sheet_detail

Read-only

Generate the QuickBooks balance sheet detail report. Returns { columns, column_types, rows }: each row has a type (section | data | total), a depth, and values aligned to columns (Money cells as numbers, first cell is the label on summary reports); id is the label cell's QuickBooks record id (e.g. the account); on detail reports ids aligns to values instead. All-zero rows are omitted and counted in hidden_zero_rows. filters lists the filters QuickBooks confirms it applied (a parameter it ignored is absent), and no_data: true means the period has nothing to report.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	No	QuickBooks report query parameters: start_date, end_date (YYYY-MM-DD) or date_macro (Today, Yesterday, This Week, Last Week, This Month, Last Month, This Month-to-date, This Fiscal Quarter, Last Fiscal Quarter, This Fiscal Year, Last Fiscal Year, This Fiscal Year-to-date, Last Fiscal Year-to-date, ...); accounting_method (Cash\|Accrual); the filters customer, vendor, item, class, department (QuickBooks Ids, comma-separated for several); account, account_type; columns (comma-separated, e.g. tx_date,txn_type,doc_num,name,memo,account_name,other_account,due_date,pmt_mthd,is_cleared,dept_name), sort_by (one of those columns), sort_order (ascend\|descend).
`company`	No	Which connected QuickBooks company to use (name, realm id, or connection id). Optional when only one company is connected.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations only declare readOnly/destructive hints; the description goes well beyond them by explaining the row type/depth structure, how ids align to label cells vs values, hidden_zero_rows counting omitted rows, the filters confirmation behavior including ignored parameters, and the no_data edge case. This is rich behavioral context that significantly informs invocation and result interpretation.

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 dense but every clause earns its place: it front-loads the return shape before diving into row semantics, id alignment, hidden rows, and filter/no_data behavior. No filler or repetition is present.

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?

There is no output schema, so the description carries full responsibility for explaining the return value, and it does so thoroughly: columns, row types, depth, id alignment, hidden rows, filter reporting, and no_data. For a read-only report tool with simple parameters, nothing essential is missing.

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

Parameters4/5

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

The input schema already documents the parameters thoroughly at 100% coverage, so the baseline is 3. The description adds extra semantic value by explaining that the filters output reflects only parameters QuickBooks actually applied and that an ignored filter parameter will be absent, plus what no_data means for the report period. This goes beyond the schema's static parameter descriptions.

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 specific verb ('Generate') and resource ('the QuickBooks balance sheet detail report'), and the return-shape details make the tool's purpose concrete. However, it does not explicitly distinguish itself from siblings like get_balance_sheet or get_balance_sheet_summary, leaving the agent to infer the difference from names and output details.

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?

The description gives no guidance about when to use this tool versus alternatives, such as get_balance_sheet_summary for summaries or get_trial_balance for a different view. The agent must infer the appropriate context solely from the tool name and the output description.

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

All Caribooks (QuickBooks Online) 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.

Resources

Need Help?