Skip to main content
Glama
wyre-technology

QuickBooks Online MCP Server

qbo_navigate

Explore available QuickBooks Online tools by selecting a business domain to see relevant actions like managing customers, invoices, and payments.

Instructions

Discover available QuickBooks Online tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesThe domain to explore: - customers: Customer management - list, get, create, and search customers - invoices: Invoice management - list, get, create invoices and send them by email - payments: Payment management - list, get, and create payments linked to invoices - vendors: Vendor management - list, get, create, update, and search vendors - items: Item management - list, get, create, update, and search products and services - accounts: Chart of accounts - list, get, create, update, and search accounts - journal_entries: Journal entries - list, get, create, update double-entry debit/credit transactions - bills: Bills - list, get, create, update, and search vendor bills (accounts payable) - bill_payments: Bill payments - list, get, create, and update payments against bills - vendor_credits: Vendor credits - list, get, create, and update credits from vendors - purchases: Direct expense purchases - list, get, create, update purchases paid at point of sale - purchase_orders: Purchase orders - list, get, create, update non-posting POs to vendors - estimates: Estimates - list, get, create, update quotes/proposals to customers - sales_receipts: Sales receipts - list, get, create, update paid-at-sale customer transactions - credit_memos: Credit memos - list, get, create, update customer credits - refund_receipts: Refund receipts - list, get, create, update cash refunds to customers - deposits: Bank deposits - list, get, create, update deposits aggregating receipts - transfers: Account transfers - list, get, create, update bank-to-bank transfers - time_activities: Time activities - list, get, create, update billable employee/vendor time - classes: Classes - list, get, create, update transaction classifications - departments: Departments - list, get, create, update business locations/divisions - terms: Payment terms - list, get, create, update terms like Net 30 - payment_methods: Payment methods - list, get, create, update payment method choices - tax_codes: Tax codes - list, get, and search (read-only) - tax_rates: Tax rates - list, get, and search (read-only) - employees: Employees - list, get, create, update, and search employees - company_info: Company info - get this QBO realm's company profile (read-only) - attachables: Attachments and notes - list, get, create, update attachment metadata, and upload files on transactions - expenses: Expense tracking - list and view purchases and bills - reports: Financial reports - profit & loss, balance sheet, aged receivables/payables, customer sales
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses that the tool returns 'tool names and descriptions' and is non-essential. It does not mention side effects or permissions, but for a read-only discovery tool, this is adequate. 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?

Three sentences, each adding value: purpose, output, and clarification. No wasted words, front-loaded with core information.

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 simple structure (one required parameter, no output schema), the description adequately covers the tool's purpose and behavior. It does not detail output format, but for a discovery aid, 'returns tool names and descriptions' is sufficient.

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 detailed enum descriptions for each domain. The description ('by domain') adds minimal 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 clearly states its role as a discovery aid for QuickBooks Online tools by domain, distinguishing it from the many CRUD/report sibling tools. It uses specific verbs ('Discover', 'Returns') and identifies the resource ('available QuickBooks Online tools by domain').

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?

The description explicitly states 'All tools are callable at any time — this is a help/discovery aid, not a prerequisite,' indicating when to use it and that it is optional. It provides clear context but does not explicitly list when not to use it or offer alternative tools for discovery.

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/wyre-technology/qbo-mcp'

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