Skip to main content
Glama

Caribooks (QuickBooks Online)

by com.caribooks
OverviewDiscussionsAdmin

List bank accounts

list_bank_accounts
Read-only

List the bank and card accounts connected on the Caribooks Banks page, with the bank's current and available balance as Caribooks last read it and the time it was read (balance_as_of), and, for each account mapped to QuickBooks, the QuickBooks account and the balance QuickBooks holds for it. Balances are read every few hours with the bank feed; this tool does not ask the bank. Tell the user how old a balance is; for a fresher one, the user presses Refresh balances on Manage banks. Read-only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyNoOnly the bank accounts mapped to this connected QuickBooks company (name, realm id, or connection id). Every bank account when left out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / live
      Removed value: -{
-  "description": "true to ask the bank for its balance now rather than its last reading.",
-  "type": "boolean"
-}
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false, openWorldHint), and the description goes well beyond them by disclosing that balances are cached, refreshed every few hours with the bank feed, and never fetched live from the bank. The staleness semantics and the resulting obligation to report balance age are exactly the kind of behavioral context annotations cannot convey.

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 purpose and payload are front-loaded in the opening sentence, and the following sentences add genuinely useful constraints (caching, freshness, user guidance). It is slightly padded by restating 'Read-only.' which the annotations already declare, keeping it just under maximum.

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

Completeness5/5

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

There is no output schema, so the description carries the return-shape burden and does so thoroughly: balances, balance_as_of timestamps, and QuickBooks mapping/balance. Combined with the freshness caveat and the optional company filter, an agent has everything needed to call it and interpret the results correctly.

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% for the single optional 'company' parameter, which already documents the name/realm-id/connection-id forms and the every-account default. The description only alludes to QuickBooks mapping in general terms and adds no filter syntax beyond the schema, so the baseline 3 applies.

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 and resource ('List the bank and card accounts connected on the Caribooks Banks page') and details exactly what each row carries: current/available balance, balance_as_of, and the mapped QuickBooks account and its balance. This clearly separates it from siblings like list_bank_feed (transactions), list_bank_transactions, and get_account_list (chart of accounts).

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?

It gives a clear use context (viewing connected account balances) plus an explicit limitation: 'this tool does not ask the bank' and the freshness workaround (user presses Refresh balances on Manage banks). It also instructs the agent to tell the user how old a balance is. It stops short of naming a sibling alternative for live/fresh data, so it is not a full 5.

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

All Caribooks (QuickBooks Online) 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