QuickBooks Desktop MCP

Overview Schema Source Related Servers Discussions Admin

qb_status

Read-only

Check QuickBooks Desktop connectivity first, then read the open company file, product edition, country, supported qbXML versions, and multicurrency settings before running accounting queries or writes.

Instructions

Call this first. Reports whether QuickBooks answers, which company file is open, product/edition/country, the qbXML versions QuickBooks supports and the one this server uses (highest <= QBBRIDGE_QBXML_MAX, default 13.0 for QuickBooks 2016), and whether multicurrency is on plus the home currency.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds meaningful depth: the tool negotiates qbXML versions ('highest <= QBBRIDGE_QBXML_MAX, default 13.0'), reports the company file, and surfaces the multicurrency flag and home currency. It stops short of saying whether an unreachable QuickBooks yields an error or a negative status value.

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 imperative 'Call this first' is front-loaded where it matters most, and each subsequent clause names a distinct returned field. The env-var/default detail ('default 13.0 for QuickBooks 2016') is slightly more granular than needed for tool selection.

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?

With no output schema, the description correctly compensates by enumerating what the call returns. The only material omission is error/failure semantics, which matters for a connectivity probe whose whole purpose is to reveal a broken connection.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. Nothing in the description conflicts with the empty schema.

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 states a specific verb ('Reports') and enumerates the exact resources returned: connectivity, open company file, product/edition/country, supported qbXML versions, and multicurrency/home currency. No sibling tool overlaps with this diagnostic role, so an agent can identify it immediately.

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

Usage Guidelines4/5

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

'Call this first' gives explicit ordering guidance that a reader cannot infer from the schema. It does not cover failure handling or say what to do if QuickBooks is unreachable, but the primary when-to-use instruction is clear.

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