lightbulb-mcp

Overview Schema Source Related Servers Discussions Admin

quickbooks_profit_loss_report

Read-onlyIdempotent

Retrieve QuickBooks profit and loss reports to analyze income statements by specifying date range, accounting method, and reporting options.

Instructions

Fetch the QuickBooks profit and loss report for income statement analysis.

Args: start_date: Report start date (YYYY-MM-DD). end_date: Report end 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
`end_date`	No
`project_id`	No
`start_date`	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.9/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds little behavioral context beyond 'Fetch', and some parameter notes like 'approval_ref ... when resuming a write' feel inconsistent with a read-only report and could confuse an agent. No direct contradiction, but behavior disclosure is minimal.

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 one-sentence purpose is front-loaded and the parameter list is cleanly formatted and scannable. It is somewhat long because 11 parameters must be documented, but every line is informative enough to justify its place, and there is no irrelevant prose.

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 report tool with an output schema, return values do not need explanation, and the parameter semantics are well covered. However, the description lacks usage guidance against alternative QuickBooks reports, does not explain the purpose of the platform plumbing parameters like project_id, project_ref, and connector_account_ref, and leaves openWorldHint behavior unaddressed.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries full responsibility for parameter meaning. It supplies useful semantics for all 11 parameters, including date formats, accounting method choices, and the required 'effect: read' constraint, going well beyond the bare schema names and types.

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 uses a specific verb ('Fetch') and resource ('QuickBooks profit and loss report') and immediately clarifies the purpose ('for income statement analysis'). This cleanly separates it from sibling QuickBooks reports like balance sheet, cash flow, and trial balance, even without naming them.

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?

The phrase 'for income statement analysis' implies when the tool is appropriate, giving some context. However, it never explicitly contrasts it with alternative QuickBooks reports or states when NOT to use it, leaving the agent to infer the decision from the report name alone.

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

Deploy Server