Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create item fixed asset

create_item_fixed_asset
Read-onlyIdempotent

Adds a fixed-asset item. Fixed-asset items represent assets that will benefit a business for longer than one year. The purchase price of these fixed assets is typically expensed over a period of years, rather than in the year the purchase was made.

The item_fixed_asset_add wrapper from qbXML is also accepted. 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, 3040 invalid_amount, 3070 string_too_long, 3100 name_in_use, 3120 object_not_found, 3140 invalid_reference, 3150 missing_element, 3175 in_use, 3176 locked, 3180 cannot_save, 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, 3263 read_only_access, 3264 merchant_services_subscription_required, 3270 missing_posting_account

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": {
      "acquired_as": "<acquired_as>",
      "name": "<name>",
      "purchase_date": "<purchase_date>",
      "purchase_desc": "<purchase_desc>"
    },
    "name": "create_item_fixed_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName is the case-insensitive short name of a list object (without ancestors). It must be unique within its hierarchy scope.
notesNoAdditional information.
bar_codeNoBarcode reference information.
locationNoWhere the asset is located or has been placed into service.
class_refNoUse classes to categorize transactions (for example, by department, location, or work type). Class tracking is off by default in QuickBooks.
is_activeNoIf `is_active` is true, this object is currently enabled for use by QuickBooks. The default value is true.
po_numberNoPurchase order number.
asset_descNoDescription of the asset—maker, brand, and so on.
cost_basisNoThe total cost of the fixed asset. This can include the cost of improvements or repairs. This amount is used to figure depreciation.
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`.
acquired_asYesIndicates whether this item was new or used when the business acquired it.
asset_numberNoThe number used by the QuickBooks Fixed Asset Manager to identify this asset.
external_guidNoAllows for the attachment of a user defined GUID value.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
purchase_costNoAmount that the QuickBooks user expects to pay when ordering or buying this item, or the amount that was actually paid for this item.
purchase_dateYesThe date when this asset was purchased.
purchase_descYesDescription that appears in the Description column of checks, bills, credit card charges, and item receipts (when an item is reordered).
serial_numberNoThe serial number of the asset.
asset_account_refNoRefers to the account QuickBooks uses to track the current value of the company’s inventory. (The AccountType of this account will be FixedAsset, OtherAsset, or OtherCurrentAsset.)
warranty_exp_dateNoThe date when the warranty for this asset expires.
include_ret_elementNo
year_end_book_valueNoA reasonable estimate of the sales value of the fixed asset, as of the end of the year.
vendor_or_payee_nameNoThe name of the vendor from whom this asset was purchased.
fixed_asset_sales_infoNoSales information, if this fixed asset was sold.
year_end_accumulated_depreciationNoThe amount the fixed asset has lost in value since it was purchased, as of the end of the year.

Output Schema

NameRequiredDescriptionDefault
urlYesReplace {connection_id} with the customer's connection.
bodyYesThe JSON body: the arguments you passed.
qbxmlNoThe qbXML it compiles to. Only with include_qbxml.
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

C2.9/5.0
Behavior1/5

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

The opening sentence asserts a create ("Adds a fixed-asset item") while annotations declare readOnlyHint=true and idempotentHint=true — a create cannot plausibly be idempotent, so an agent may believe a record is written and later re-run it. The later sentence about returning "the v2 request to send" hints at a compile-only operation, but it is buried and does not repair the leading mutation claim, leaving the tool's actual effect contradictory.

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?

Purpose and the fixed-asset definition are front-loaded, which is good, but roughly half the text is an undifferentiated run-on list of 25 error code/type pairs that costs many tokens and is only marginally actionable. The valuable line about the returned v2 request and webhook payload is buried mid-paragraph.

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

Completeness3/5

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

For a 25-parameter create with an output schema, the description does cover the response model (v2 request plus webhook payload with response_json) and enumerates likely failure codes, which is genuinely useful. However, it never resolves the central question of whether the tool actually submits the create or merely compiles a request, and it omits permission/authorization expectations beyond the error list.

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 96% across 25 parameters, so the schema already carries the semantics and baseline 3 applies. The description adds only one schema-adjacent convention — that the qbXML `item_fixed_asset_add` wrapper name is accepted — and says nothing about the four required fields or the include_qbxml / include_ret_element options.

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 description names a specific verb and resource ("Adds a fixed-asset item") and adds a domain definition — assets benefiting the business for more than a year, expensed over multiple years — that meaningfully separates it from inventory or non-inventory item creation. It never names or contrasts a sibling such as update_item_fixed_asset or create_item_inventory, so an agent must infer routing from the CRUD verb alone.

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 conceptual explanation of what a fixed asset is implies when the tool applies, but there is no explicit when-to-use / when-not-to-use statement and no alternative is named. Prerequisites such as required permissions or whether an asset account must already exist are left unstated.

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