QuickBooks Online MCP Server

search_departments

Find departments in QuickBooks Online using optional filters for name, active status, and result limit. Retrieve matching department records to support reporting and categorization.

Instructions

Search for departments 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_departments"
  }
}

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 supplied, so the description carries the full behavioral burden. 'Search' implies a read-only operation, but nothing is said about pagination defaults, maximum page size, what happens when no filters are passed, or what the response contains. For a listing tool with a limit parameter, this is a meaningful gap.

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 filler or redundancy. It is efficient, though its brevity is partly the cause of the gaps in other dimensions.

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, no output schema, and a nested params object, the description needed to explain read-only behavior, filter semantics, and result/pagination behavior. It supplies none of these, leaving an agent to infer everything beyond the entity name.

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?

The description only says 'optional filters' and does not name or explain name, limit, or active. The nested schema properties do carry short descriptions, but overall coverage is reported at 0% at the top level, so the description should have enumerated the available filters to compensate.

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 names a specific verb (search) and resource (departments) and scopes it to QuickBooks Online, so the agent knows exactly what entity is queried. It stops short of distinguishing itself from siblings like get_department, create_department, or search_classes, which share the same domain.

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?

The only usage signal is the phrase 'with optional filters', which implies a list/search operation but gives no conditions for choosing it over get_department (single record) or search_classes (analogous entity). There are no exclusions, prerequisites, or notes about when filters are required.

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

Deploy Server