Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create date driven terms

create_date_driven_terms
Read-onlyIdempotent

Date-driven terms show the day of the month by which payment is due and can include a discount for early payment. For example, the following date-driven term means that payment is due on the 30th of the month, with a 1% discount if payment is made by the 10th:

The date_driven_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": {
      "day_of_month_due": "<day_of_month_due>",
      "name": "<name>"
    },
    "name": "create_date_driven_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 by `discount_day_of_month`, then this discount will apply to the payment. `discount_pct` must be between 0 and 100.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
day_of_month_dueYesThe day of the month when full payment is due with no discount.
due_next_month_daysNoHandles cases when an invoice or bill is issued close to its due date. If the invoice or bill is issued within this many days of the due date, payment isn’t due until the following month.
include_ret_elementNo
discount_day_of_monthNoIf the payment is made by this day of the month, then `discount_pct` applies.

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

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description usefully reconciles the 'create' name with that by disclosing that the call returns the v2 request to send plus the webhook payload shape rather than executing the write itself — a genuinely non-obvious two-step async pattern. It also enumerates the error codes (e.g. 3100 name_in_use, 3176 locked, 3263 read_only_access) an agent must handle. Minor deduction for the bombastic error list and for not stating whether name uniqueness is enforced at create time.

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 defines the concept rather than the operation, so the actual purpose is not front-loaded. The illustrative example is broken off at a dangling colon ('with a 1% discount if payment is made by the 10th:') with no figure or payload following, which wastes space, and the 18-code error dump is long though arguably operationally useful.

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?

With an output schema present, return values do not need explaining, and annotations plus the description together cover safety and the async webhook flow. Still missing are an explicit statement of what is created and guidance on choosing this tool over the date-driven-terms lookup or standard-terms siblings, which matters given the dense `create_*` catalog.

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 89%, so parameters like `name`, `discount_pct`, `day_of_month_due`, and `due_next_month_days` are already well documented in the schema. The description adds conceptual meaning by explaining how the due day and early-payment discount interact, but it adds nothing for `request_id`, `include_qbxml`, or `include_ret_element`. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explains the domain concept of date-driven terms (due day of month plus optional early-payment discount) and notes that a qbXML `date_driven_terms_add` wrapper is accepted, so the resource is identifiable. However, it never states plainly that this tool creates a new date-driven terms object, and it does not distinguish itself from the `find_date_driven_terms` or `create_standard_terms` siblings. The verb+outcome must be inferred from the tool name alone.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as `find_date_driven_terms` for lookup or `create_standard_terms` for standard (non-date-driven) terms. The only routing hint is implicit in the domain explanation of what a date-driven term is.

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