Skip to main content
Glama

CorpusIQ

by io.corpusiq
OverviewDiscussionsAdmin

Quickbooks Connector

quickbooks_connector
Read-onlyIdempotent

Financial accounting: profit & loss, invoices, balance sheet, accounts receivable/payable, payments, expenses, vendors, customers, and financial reports. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesget_profit_loss: Get Profit and Loss (Income Statement) report | list_invoices: List invoices with optional date filters | get_overdue_invoices: Get overdue invoices with open balance, sorted by days overdue | get_balance_sheet: Get Balance Sheet report: assets, liabilities, equity | get_company_info: Get QuickBooks company profile: name, address, fiscal year, industry | list_customers: List QuickBooks customers with pagination | get_customer: Get full details for a single QuickBooks customer | search_customers: Search QuickBooks customers by display name | get_invoice: Get full details for a single QuickBooks invoice | search_invoices: Search invoices by customer name or invoice number | list_payments: List payments received with optional date filters | get_payment: Get full details for a single QuickBooks payment | list_items: List products and services (items) in QuickBooks | list_accounts: List chart of accounts from QuickBooks | list_vendors: List vendors (suppliers) in QuickBooks | list_bills: List bills (payables) with optional date filters | get_ar_aging: Get Accounts Receivable Aging report by age bucket | get_ap_aging: Get Accounts Payable Aging report by age bucket
paramsNoAction-specific parameters. get_profit_loss: {start_date?: string, end_date?: string} | list_invoices: {max_results?: integer, start_position?: integer, start_date?: string, end_date?: string} | get_overdue_invoices: {max_results?: integer} | get_balance_sheet: {end_date?: string} | get_company_info: none | list_customers: {max_results?: integer, start_position?: integer} | get_customer: {customer_id: string} | search_customers: {query: string, max_results?: integer} | get_invoice: {invoice_id: string} | search_invoices: {query: string, max_results?: integer} | list_payments: {max_results?: integer, start_position?: integer, start_date?: string, end_date?: string} | get_payment: {payment_id: string} | list_items: {max_results?: integer, start_position?: integer} | list_accounts: {max_results?: integer, start_position?: integer, account_type?: string} | list_vendors: {max_results?: integer, start_position?: integer} | list_bills: {max_results?: integer, start_position?: integer, start_date?: string, end_date?: string} | get_ar_aging: {end_date?: string} | get_ap_aging: {end_date?: string}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses a real behavioral contract: verified vs unverified data labeling, a 15-minute provenance token valid across replicas, and mandatory attribution footer handling. That is meaningful context. It stops short of describing pagination or return shape, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, which is good, but roughly half the text is boilerplate contract language (provenance, attribution footer, accuracy rules) that is dense and partly redundant. The length is not proportionate to a description whose parameters are already fully documented in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-action read-only connector with no output schema, the description covers the domain, the downstream visualization path, provenance semantics, and explicit accuracy constraints. Return formats and pagination are left implicit, but the schema carries the action detail and the annotations carry safety, so the important gaps are minor.

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?

Schema description coverage is 100%: every action enum value and its param signature is documented in the schema itself. The description adds no per-action or per-parameter meaning beyond that, so the baseline 3 applies.

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 enumerates the financial resources handled (P&L, invoices, balance sheet, AR/AP, payments, expenses, vendors, customers, reports), which is specific and maps directly onto the action enum. It does not explicitly differentiate this connector from financial siblings like quickbooks_dashboard or stripe_dashboard, but the accounting scope is clear enough for selection.

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?

It gives strong downstream routing guidance ('When the user asks for a visual, trend, comparison, or recap, call chart_render...'), but that governs a sibling tool, not this one. There is no explicit statement of when to prefer this connector over quickbooks_dashboard or when not to use it, so usage is only implied.

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

All CorpusIQ toolsInspect
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