QuickBooks Online MCP Server

create_purchase

Creates a purchase record in QuickBooks Online so you can log expenses and maintain accurate financial records.

Instructions

Create a purchase in QuickBooks Online.

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": "create_purchase"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

D1.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 disclosure burden, and it only conveys that this is a creation (write) operation. It says nothing about required business fields, whether the purchase posts to the ledger immediately, permission or OAuth-scope requirements, or irreversibility of the write.

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 description is a single short sentence with no filler, so nothing is wasted. However, its brevity reflects under-specification rather than disciplined economy, and it front-loads nothing beyond the verb and resource.

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

Completeness1/5

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

This is a nested-object mutation tool with no annotations, no output schema, and 0% schema description coverage, yet the description is one tautological sentence. An agent cannot construct a valid call or predict the result from the definition as given.

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

Parameters1/5

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

There is one parameter, "purchase," defined as an unconstrained object with zero schema description coverage, and the description adds no meaning about its expected shape or fields. The single sentence provides no compensating detail, leaving the caller to guess the entire payload contract.

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

Purpose2/5

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

The sentence restates the tool name ("Create a purchase") and only adds the product context "in QuickBooks Online." It gives no indication of what a Purchase entity actually represents in QBO (expense, check, or vendor transaction) or how it differs from the many sibling creation tools such as create_bill, create_purchase_order, or create_vendor_credit.

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

Usage Guidelines1/5

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

There is no when-to-use guidance at all. With roughly 130 siblings including create_bill, create_purchase_order, create_expense-style flows, and update_purchase/get_purchase/search_purchases, an agent has no basis for choosing this tool over a near-neighbour.

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

Deploy Server