Caribooks (QuickBooks Online)

Create a sales tax code

create_tax_service

Destructive

Create a sales tax code in QuickBooks Online, with new or existing tax rates attached to it. A rate created here has no tax return line, so its tax is left off the sales tax return; a rate that must be reported is created in QuickBooks' own sales tax settings. Cannot be undone; only on an explicit request.

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": {
      "entity": "<entity>"
    },
    "name": "create_tax_service"
  }
}

Input Schema

Name	Required	Description	Default
`entity`	Yes	The TaxService to create, as a QuickBooks Online API v3 TaxService object. Do not send government identifiers (SSN or tax IDs), birth dates or card-processing details. Manage those fields directly in QuickBooks. { TaxCode: '<new code name>', TaxRateDetails: [{ TaxRateName, RateValue (0-100), TaxAgencyId (an existing TaxAgency Id), TaxApplicableOn: 'Sales'\|'Purchase' }] }, or TaxRateId to reuse an existing rate. A tax code or rate cannot be deleted once created, only made inactive. Only create one when the user has asked for it.
`company`	No	Which connected QuickBooks company to use (name, realm id, or connection id). Optional when only one company is connected.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 21, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds the concrete consequence: the change cannot be undone and the rate's tax is omitted from the return. That downstream reporting effect is behavior an agent could not infer from annotations or schema, and it reinforces rather than contradicts the destructive hint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: the action first, then the reporting consequence, then the irreversibility/consent constraint. No restatement of the title or schema, and every clause carries decision-relevant information.

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?

For a nested-object mutation with no output schema, the description covers the critical unknowns: irreversibility, downstream tax-return impact, and the explicit-request gate. Minor gaps remain — it doesn't say what happens on duplicate codes or what the call returns — but nothing essential for safe invocation is missing.

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 100% and the entity schema description already spells out TaxCode, TaxRateDetails fields (RateValue range, TaxApplicableOn values) and the TaxRateId reuse path. The description adds only the 'new or existing rates' framing, so it neither needs to nor does add parameter detail beyond the schema — baseline 3.

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

Purpose5/5

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

States a specific verb and resource ('Create a sales tax code in QuickBooks Online') and clarifies that tax rates can be created alongside it or reused by id. This clearly separates it from sibling creation tools such as create_tax_agency and from read-side siblings like get_tax_code/get_tax_rate.

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

Usage Guidelines5/5

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

Explicitly states when NOT to create the rate here: a rate created this way has no tax return line and its tax is left off the sales tax return, so reportable rates belong in QuickBooks' own sales tax settings. It adds the gating condition 'only on an explicit request', which is an unusual and valuable exclusion for a create tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Caribooks (QuickBooks Online) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?