QuickBooks Online MCP Server

report_cash_flow

Generates a Statement of Cash Flows report showing operating, investing, and financing activities for a chosen date range, with accounting method, summarization, and entity filters.

Instructions

Run a Statement of Cash Flows report showing operating, investing, and financing activities. Supports date range, accounting method, summarization, and filters.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It identifies the report sections but does not state that the operation is read-only, describe the returned data shape, mention pagination, or explain authorization or data-scope constraints.

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 two compact sentences, front-loaded with the report identity and followed by the supported capability groups. There is no filler or redundant phrasing.

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?

For a complex report tool with a nested params object and no output schema, the description covers the core activity sections and broad feature groups. It leaves gaps around return format, row/column structure, and how filters and date_macro interact, so it is adequate but not fully complete.

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 input schema itself thoroughly documents the nested properties, including date_macro, start_date/end_date, accounting_method, summarize_column_by, and filter fields. The description only summarizes parameter categories and adds no syntax, constraints, or default behavior beyond what the schema already provides, so the baseline of 3 is appropriate.

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 uses a specific verb, 'Run', and a specific resource, 'Statement of Cash Flows report', and names the operating, investing, and financing sections. It is clear what the tool produces, though it does not explicitly contrast itself with sibling report_* tools.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no comparison to related reports such as report_profit_and_loss or report_balance_sheet. The report name implies its purpose, but an agent gets no help choosing among report tools or understanding prerequisites.

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

Deploy Server