Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create standard terms

create_standard_terms
Read-onlyIdempotent

Adds a standard term. Standard terms show the number of days within which payment is due and can include a discount for early payment. For example, the following standard term means that payment is due in 30 days, with a 1% discount if payment is made within 10 days:

The standard_terms_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, 3040 invalid_amount, 3070 string_too_long, 3100 name_in_use, 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": {
      "name": "<name>"
    },
    "name": "create_standard_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName is the case-insensitive short name of a list object (without ancestors). It must be unique within its hierarchy scope.
is_activeNoIf `is_active` is true, this object is currently enabled for use by QuickBooks. The default value is true.
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`.
discount_pctNoIf payment is received within `std_discount_days` number of days, then this discount will apply to the payment. `discount_pct` must be between 0 and 100.
std_due_daysNoThe number of days until payment is due.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
std_discount_daysNoIf payment is received within `std_discount_days` number of days, then `discount_pct` will apply to the payment.
include_ret_elementNo

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

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, which makes sense once the description reveals that this compiles a v2 request and returns the webhook payload shape rather than mutating state directly. The description adds genuinely non-obvious behavior: the qbXML `standard_terms_add` wrapper alias, the response_json shape, and a full error-code/type catalog including permission and feature-gating codes. It still doesn't say whether a submitted request can fail after acceptance or how long the webhook takes.

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 key facts (adds a term, returns a v2 request plus webhook shape) are front-loaded, which is good. However, the sentence introducing the example ends with a colon and no example follows, which is a visible structural defect, and the 20-entry error enumeration is dense relative to the rest of the text.

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?

An output schema exists, so return values need less explanation, yet the description still characterizes the response_json and the error surface, which is more than required. What's missing for a create tool is the boundary against the date-driven-terms sibling and any note on uniqueness constraints, though the name parameter's own schema text covers the latter.

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 88%, so the schema already documents nearly every parameter, which sets the baseline at 3. The one real addition is the worked example showing how std_due_days, std_discount_days, and discount_pct interact (30 days due, 1% if paid in 10) — but the example is truncated and no concrete field values are shown.

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 opens with a specific verb and resource ("Adds a standard term") and immediately explains what a standard term is: days-until-due plus an optional early-payment discount. That is far more than a restatement of the name. It stops short of distinguishing this from siblings like create_date_driven_terms, so an agent cannot tell from the text alone which terms type to pick.

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?

There is no explicit when-to-use or when-not-to-use statement, and no named alternative (find_standard_terms, create_date_driven_terms) is referenced. Usage is only implied by the domain definition of a standard term as day-based with an optional discount, which a careful agent can read as the selection criterion.

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