Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Find sales tax payables

find_sales_tax_payables
Read-onlyIdempotent

Builds a v2 sales_tax_payable.query request.

Returns the v2 request to send, and the webhook payload QuickBooks' answer arrives in (this operation's response_json: its data shape and the status codes to handle).

Possible errors (error.code / error.type; the call result explains each): 1030 unsupported_request, 3150 missing_element, 3210 invalid_value, 3220 not_authorized, 3231 request_not_processed, 3250 feature_not_enabled, 3260 insufficient_permission, 3261 personal_data_access_denied, 3262 payroll_subscription_required, 3264 merchant_services_subscription_required

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": "find_sales_tax_payables"
  }
}

Input Schema

NameRequiredDescriptionDefault
meta_dataNoUse the `meta_data` attribute to control whether query responses include counts. Options are NoMetaData (default), MetaDataOnly (count only), and MetaDataAndResponseData (count plus objects).
as_of_dateNoThe date when the exchange rate was last changed.
request_idNoYour own label for the request, sent to QuickBooks as its qbXML `requestID` and echoed in the raw answer (`response_xml`); optional, since the answer's webhook already carries the request's `id`.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
include_ret_elementNo

Output Schema

NameRequiredDescriptionDefault
urlYesReplace {connection_id} with the customer's connection.
qbxmlNoThe qbXML it compiles to. Only with include_qbxml.
queryYesThe query parameters: the arguments you passed.
methodYes
headersYesSend with the request. Resent unchanged when no 201 came back, it answers with the request already queued.
webhookYesJSON Schema of the payload POSTed to webhook_url once QuickBooks answers, with this operation's response_json (data shape and status codes).

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?

Annotations already cover the safety profile (read-only, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious behavior beyond that: the tool returns a v2 request plus a webhook payload descriptor rather than the data itself, and it enumerates the error codes the caller may encounter. It stops short of explaining how the request must be forwarded or how the webhook response is correlated.

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?

The opening sentence is well front-loaded, but the second sentence is dense and awkwardly parenthesized ('this operation's response_json: its data shape and the status codes to handle'), and the ten-item error enumeration is bulky despite the description conceding 'the call result explains each' — a pointer to the error catalog would have sufficed.

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 an output schema present, the description rightly focuses on the non-obvious mechanics: that the return value is a request to dispatch and that the answer arrives asynchronously via webhook, plus error handling. All five parameters are optional, so the missing dispatch/webhook-setup details are the only meaningful gap.

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 80%, so the schema already explains meta_data, as_of_date, request_id, and include_qbxml. The description adds no parameter-level meaning at all, and the one undocumented element — the include_ret_element item enum — receives no clarification here. Baseline 3 is appropriate given the schema does the heavy lifting.

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 first sentence names a specific verb and resource: it 'builds a v2 sales_tax_payable.query request,' which importantly corrects the misleading 'find_' prefix by making clear this tool constructs a request rather than fetching payables. It does not, however, contrast itself with adjacent siblings such as find_sales_tax_returns or find_sales_tax_return_lines.

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?

Usage is implied rather than stated: the reader can infer the pattern of build-a-request-then-receive-a-webhook, but there is no explicit when-to-use guidance, no prerequisites such as webhook configuration, and no indication of when a sibling lookup tool would be preferable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources