QuickBooks Online MCP Server

create_refund_receipt

Create customer refund receipts in QuickBooks Online by specifying the customer, line items, payment method, and deposit account.

Instructions

Create a refund receipt (customer refund) 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_refund_receipt"
  }
}

Input Schema

Name	Required	Description	Default
`params`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only implies that this is a write operation through the word "Create." It does not disclose financial side effects, account or payment behavior, permissions, error behavior, or what happens after creation.

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?

The single sentence is front-loaded, clear, and free of filler, with a useful parenthetical clarifying the resource. Its brevity leaves no room for operational caveats, but the wording itself is efficient.

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?

For a complex financial-creation tool with nested inputs, no annotations, and no output schema, one purpose sentence is insufficient. Important selection, prerequisite, behavioral, and invocation context is missing, even though the schema supplies field shapes and constraints.

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?

The description adds no parameter guidance beyond the schema, despite the reported 0% schema description coverage and nested input structure. It does not explain the params wrapper, the required customer_ref and line_items values, how to obtain reference IDs, or how pricing and tax fields interact.

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—creating a refund receipt in QuickBooks Online—and clarifies that this means a customer refund. It does not explicitly distinguish the operation from sibling tools such as create_credit_memo or create_sales_receipt.

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

Usage Guidelines3/5

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

The phrase "customer refund" implies the general situation in which the tool is used. However, there is no guidance on when a refund receipt is appropriate versus a credit memo, payment, or sales receipt, nor any prerequisites for invocation.

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

Deploy Server