QuickBooks Online MCP Server

search_tax_codes

Search QuickBooks Online tax codes by name, active status, or taxable status, and set a result limit to retrieve the tax codes needed for accounting and reporting tasks.

Instructions

Search for tax codes in QuickBooks Online with optional filters.

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": {
      "params": "<params>"
    },
    "name": "search_tax_codes"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden and it says nothing about read-only behavior, default result limits, pagination, or what an empty result set looks like. The only behavioral hint is "optional filters", which the schema already implies.

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

Conciseness4/5

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

A single front-loaded sentence with no wasted words. It is efficient, though its brevity comes at the cost of the missing detail noted elsewhere.

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

Completeness2/5

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

With no annotations and no output schema, the description should explain the result shape, default/max limits, and pagination behavior for a filtered list call, and it does none of these. The nested params object also goes unmentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Reported schema description coverage is 0% at the top level and the description names no filters at all, so it fails to compensate for the coverage gap. It does not explain what happens when filters are omitted or how the nullable boolean filters (active, taxable) are interpreted.

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 uses a specific verb and resource ("Search for tax codes") and scopes it to QuickBooks Online, so an agent can tell it is a lookup tool for tax codes. It does not differentiate itself from the sibling get_tax_code or search_tax_rates, which is why it stops short of a 5.

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?

Beyond noting that filters are optional, the description gives no guidance on when to use this instead of get_tax_code (single-record fetch) or search_tax_rates. The search-vs-get distinction is only implied by the verb choice.

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

Deploy Server