Quickbooks

Qb List Accounts

qb_list_accounts

Read-onlyIdempotent

Get your chart of accounts with account names, types (asset/liability/equity/etc), balances, and classifications.

Input Schema

Name	Required	Description	Default
`max_results`	No	Maximum number of accounts to return (default 100, max 1000)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 13, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "oneOf": [
+    {
+      "properties": {
+        "error": {
+          "description": "Error code if connection not configured",
+          "type": "string"
+        },
+        "message": {
+          "description": "Error message with setup instructions",
+          "type": "string"
+        }
+      },
+      "required": [
+        "error",
+        "message"
+      ],
+      "type": "object"
+    },
+    {
+      "properties": {
+        "QueryResponse": {
+          "description": "Array of accounts with names, types, balances, and classifications",
+          "items": {
+            "properties": {
+              "AccountType": {
+                "description": "Account type (asset/liability/equity/etc)",
+                "type": "string"
+              },
+              "CurrentBalance": {
+                "description": "Current account balance",
+                "type": "number"
+              },
+              "Id": {
+                "description": "Account ID",
+                "type": "string"
+              },
+              "Name": {
+                "description": "Account name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    }
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026
- addedInput schema / examples
```
Added value: +[
+  {
+    "max_results": 100
+  }
+]
```
First observedApr 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by specifying the returned fields (account names, types, balances, classifications), which helps the agent understand what data to expect. No contradictions with annotations.

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

Conciseness5/5

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

A single sentence that efficiently conveys purpose and key data fields with no wasted words. Perfectly front-loaded.

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?

Given the tool's simplicity (one optional param, no nested objects) and the presence of an output schema, the description adequately covers purpose and output. It could mention pagination or how to get all accounts, but it is generally complete for a read-only list tool.

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 coverage is 100% with a good description of the max_results parameter (default and max). The description does not add additional meaning beyond the schema, so baseline 3 is appropriate.

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 'Get' and clearly identifies the resource 'chart of accounts', listing key data fields (names, types, balances, classifications). This distinguishes it from sibling tools like qb_query which are more generic.

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 description implies its use for retrieving chart of accounts but offers no explicit guidance on when to prefer this over alternatives (e.g., qb_query). No exclusions or when-not-to-use advice is provided.

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

All Quickbooks tools Inspect

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.