Skip to main content
Glama

quickbooks_report

Fetch QuickBooks financial reports like profit and loss or balance sheet by specifying report name, date range, and accounting method.

Instructions

Fetch a named QuickBooks report such as profit_loss, balance_sheet, cash_flow, trial_balance, ar_aging, or ap_aging.

Args: report_name (required): QuickBooks report name or alias. start_date: Report start date (YYYY-MM-DD). end_date: Report end date (YYYY-MM-DD). as_of_date: Report as-of date for balance/aging reports (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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
report_nameNo
start_dateNo
end_dateNo
as_of_dateNo
accounting_methodNo
summarize_column_byNo
columnsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description indicates a read-only fetch operation and clarifies parameter usage (e.g., as_of_date for balance reports). However, no annotations exist, and the description omits details on error handling, auth, or side effects.

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 structured with clear 'Args:' and bullet points. It is slightly verbose but each sentence adds value, focusing on parameter details.

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?

While the description covers parameters well, it lacks context about sibling report tools and when to use this generic version. Given that dedicated tools exist, this gap reduces completeness.

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?

With 0% schema coverage, the description adds essential meaning: report_name is required, date formats, and parameter purposes. It could be improved with enums for report_name and summarize_column_by, but is largely effective.

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 clearly states it fetches a named QuickBooks report and lists examples. However, it does not differentiate from sibling specific report tools like quickbooks_profit_loss_report, which could confuse an agent.

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 on when to use this generic tool versus the specific report tools (e.g., quickbooks_balance_sheet_report). The agent receives no help in choosing between alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RPasquale/lightbulb-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server