QuickBooks Desktop MCP

Overview Schema Source Related Servers Discussions Admin

qb_add_vendor

Creates a QuickBooks Desktop vendor with a two-step preview and confirmation; rejects exact duplicate names, so list existing vendors first to avoid near-duplicates.

Instructions

Creates a vendor. Two steps (preview + confirm_code). Refuses if a vendor with this exact name exists; check qb_list_vendors first for near-duplicates in spelling/casing.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`run_id`	No
`confirm_code`	No
`expected_company_file`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

It explicitly discloses the two-step nature of the process ('preview + confirm_code'). This is crucial workflow information that is not present in the input schema or standard annotations, giving the agent advanced operational knowledge.

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?

The description is highly efficient. Both sentences deliver critical, non-redundant operational information without waste, making it front-loaded with utility.

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

Completeness5/5

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

Given the complexity and the lack of schema coverage, the description covers all necessary functional context: what it does, how it works (2 steps), and how to safely invoke it (pre-check for duplicates).

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?

Since schema description coverage is 0%, the description is required to add semantic value. However, the description focuses on process flow and error handling rather than explaining the purpose or structure of the four defined parameters.

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?

The purpose is clearly stated: 'Creates a vendor.' It distinguishes itself from sibling tools like qb_list_vendors by defining a creation workflow.

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?

It provides explicit usage constraints, telling the agent it 'Refuses' if the name exists and instructing it to check qb_list_vendors first for potential near-duplicates.

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