lightbulb-mcp

Overview Schema Source Related Servers Discussions Admin

quickbooks_balance_sheet_report

Read-onlyIdempotent

Fetch a QuickBooks balance sheet report as of a specified date, with options for accounting method and column customization.

Instructions

Fetch the QuickBooks balance sheet report as of a date.

Args: as_of_date: Report as-of date (YYYY-MM-DD). accounting_method: Accounting method: Accrual or Cash. summarize_column_by: Optional QuickBooks summarize_column_by parameter. columns: Optional report columns to request. project_id: Authenticated Project UUID. project_ref: Exact project correlation reference. connector_account_ref: Project-bound connector account alias. idempotency_key: Stable business-action identity. effect: Required and must be read; Spring verifies it. approval_ref: Approved platform task UUID when resuming a write.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`effect`	Yes
`columns`	No
`as_of_date`	No
`project_id`	No
`project_ref`	No
`approval_ref`	No
`idempotency_key`	No
`accounting_method`	No
`summarize_column_by`	No
`connector_account_ref`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.1Sep 7, 2026

addedInput schema / properties / approval_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Approval Ref"
+}

addedInput schema / properties / connector_account_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Connector Account Ref"
+}

addedInput schema / properties / effect

Added value: +{
+  "const": "read",
+  "title": "Effect",
+  "type": "string"
+}

addedInput schema / properties / idempotency_key

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Idempotency Key"
+}

addedInput schema / properties / project_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Id"
+}

addedInput schema / properties / project_ref

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Project Ref"
+}

addedInput schema / required
```
Added value: +[
+  "effect"
+]
```

First observedv0.1.0Jun 25, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds that effect must be 'read' and that Spring verifies it, but the approval_ref note about 'resuming a write' is extraneous and slightly confusing for a read-only report tool. There is no direct contradiction with the annotations.

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?

The description is a one-sentence purpose followed by a compact Args list with no filler. It is somewhat lengthy due to boilerplate platform parameters, but each parameter earns its place given the complete absence of schema descriptions.

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?

The description explains the main report inputs and can rely on the output schema for return-value details. It does not indicate which parameters are practically required beyond effect (e.g., as_of_date, connector_account_ref/project_id) or when this report should be preferred over its sibling report tools.

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 schema has no parameter descriptions, so the Args list carries the full burden and does cover all 10 parameters with useful specifics like as_of_date format and accounting_method values. Some entries are generic or tautological (summarize_column_by, project_ref), preventing a perfect score.

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 opening sentence 'Fetch the QuickBooks balance sheet report as of a date' clearly identifies the verb, resource, and temporal scope. It does not explicitly differentiate from sibling report tools like quickbooks_profit_loss_report or quickbooks_cash_flow_report, but the balance sheet resource is unambiguous.

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

Usage Guidelines3/5

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

No explicit when-to-use guidance or alternative tool exclusions are provided; an agent must infer that this is the right tool when a balance sheet is requested. Given the many sibling report tools, the absence of explicit differentiation is a meaningful gap.

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

Deploy Server