Skip to main content
Glama

QuBe Sync: QuickBooks Desktop API for developers

Create currency

create_currency
Read-onlyIdempotent

Creates a user defined currency with the specified name and currency code, both of which will show up in the QuickBooks UI.

The currency_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": {
      "currency_code": "<currency_code>",
      "name": "<name>"
    },
    "name": "create_currency"
  }
}

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`.
currency_codeYesFor built-in currencies, the currency code and name is the generally accepted code and name. These are based on the standard ISO 4217 code/name for a country’s currency.
include_qbxmlNoAlso return the qbXML this compiles to, for debugging. Not part of the v2 request.
currency_formatNoThe aggregate controlling the appearance of the currency with regard to comma and decimal.
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

B3.1/5.0
Behavior3/5

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

The description adds real behavior beyond the annotations: it discloses the return contract (the v2 request to send plus the webhook payload the answer arrives in) and enumerates error codes with their types, which is useful for handling failures. However, it frames the operation as creating a currency that "will show up in the QuickBooks UI" while annotations declare readOnlyHint=true and destructiveHint=false; the mechanism that reconciles this (the tool compiles a request rather than mutating data) is only implied, in one convoluted sentence, so the agent is left unsure whether calling it has side effects.

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 in one clean sentence, but the second sentence is garbled ("and the webhook payload QuickBooks' answer arrives in (this operation's response_json: its data shape and the status codes to handle") and forces the reader to parse the return contract out of a parenthetical. The block of twenty error codes is dense prose that would read far better as structured data and consumes roughly half the description.

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?

An output schema exists, yet the description still usefully explains the async request/webhook-answer model that the schema cannot convey, and it covers failure modes well. What is missing for a 7-parameter, nested-object creation tool is clarity on side effects and execution model, which matters more here than the optional fields the schema already documents.

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 86%, so the schema already carries most parameter meaning and baseline 3 applies. The description reinforces that name and currency_code are the identifying fields and the error list hints at constraints (name_in_use implies uniqueness, string_too_long implies length limits), but optional parameters such as is_active, include_qbxml, currency_format, and include_ret_element get no mention.

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 verb and resource ("Creates a user defined currency") plus the two key inputs (name, currency code) and the scope distinction that it is a user-defined rather than built-in currency. It does not name or differentiate against update_currency, the obvious sibling, leaving that routing to inference.

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 statement of when to use this versus update_currency, no prerequisites (permissions, feature enablement, whether the currency must already not exist), and no exclusions. The only alternative mentioned, the qbXML `currency_add` wrapper, is an input-shape alias rather than a tool-selection alternative.

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