QuickBooks Online MCP Server

get_refund_receipt

Retrieve a single QuickBooks Online refund receipt by its ID to view refund details, verify transactions, and support reconciliation.

Instructions

Get a single refund receipt by ID from 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": "get_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.9/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 behavioral burden, and it discloses nothing beyond the word 'Get'. It does not say whether the call is read-only, what happens if the ID is missing or invalid, whether it returns a full or partial record, or what permission/auth requirements apply.

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?

It is a single, front-loaded sentence with no filler or redundancy. It could carry more payload at the same length, but nothing in it is wasted.

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?

The tool is simple (one parameter, no nested return schema, no annotations), yet with no output schema the description should say what a refund receipt record looks like or at least that the full record is returned. Neither that nor any failure-mode context is present, leaving the definition thin even for a simple lookup.

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?

There is one parameter with effectively zero description coverage beyond a bare label in the schema, so the description must compensate. 'By ID' adds no meaning over the schema's 'id' field, and nothing is said about ID format, source, or the nested params wrapper.

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 states a specific verb and resource ('Get a single refund receipt') and pins the lookup method ('by ID'), which separates it from search_refund_receipts. It does not name any sibling explicitly, but the 'single ... by ID' phrasing is enough for an agent to tell it apart from search/create/update/delete variants.

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 'by ID' implies the caller must already have the refund receipt ID, so usage is implied rather than stated. There is no explicit guidance on when to use this versus search_refund_receipts, and no mention of prerequisites or error behavior when the ID is unknown.

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

Deploy Server