Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Find item assemblies can builds

find_item_assemblies_can_builds
Read-onlyIdempotent

A query that is used to determine the current number of the specified assembly that can be built from the components on hand.

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, 3000 invalid_object_id, 3120 object_not_found, 3140 invalid_reference, 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

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "item_inventory_assembly_ref": "<item_inventory_assembly_ref>",
      "txn_date": "<txn_date>"
    },
    "name": "find_item_assemblies_can_builds"
  }
}

Input Schema

NameRequiredDescriptionDefault
txn_dateYesThe date of the transaction. In some cases, if you leave `txn_date` out of an -Add message, QuickBooks will prefill `txn_date` with the date of the last-saved transaction of the same type.
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.
item_inventory_assembly_refYesAn inventory assembly item is one that is assembled or manufactured from inventory items. The items and/or assemblies that make up the assembly are called components.

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

B3.4/5.0
Behavior4/5

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

Beyond readOnly/openWorld/idempotent/destructive annotations, it discloses the non-obvious async behavior: the call returns a v2 request plus the webhook payload envelope and status codes. It also enumerates possible error codes, though it omits auth and rate-limit details.

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 purpose is front-loaded and the async-response note earns its place, but the long list of 14 error codes dominates the description and is more verbose than needed for selection or invocation. Structure is readable but not tight.

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 an output schema and full parameter coverage, the description need not restate field definitions. It adds the crucial async request/webhook flow and error landscape for this QuickBooks operation; only sibling selection guidance and prerequisites are notably absent.

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%, so the input schema already defines txn_date, request_id, include_qbxml, and the assembly reference including list_id/full_name. The description adds only 'specified assembly'/'components on hand' context and no parameter-specific semantics beyond the schema.

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 gives a specific operation: determining how many of a specified inventory assembly can be built from on-hand components. That is more than a restatement of the name, but it does not differentiate the tool from siblings like find_item_inventory_assemblies or find_build_assemblies.

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

Usage Guidelines2/5

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

The description supplies a use case but no explicit when-to-use/when-not rules, prerequisites, or named alternatives among the many find_item_* and assembly-related siblings. An agent must infer selection from the purpose sentence alone.

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