QuickBooks Online MCP Server

create_transfer

Create a bank transfer between QuickBooks Online accounts to move funds by specifying source and destination accounts, amount, and optional date or note.

Instructions

Create a bank transfer between accounts 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_transfer"
  }
}

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?

With no annotations provided, the description carries the full burden and discloses almost nothing behavioral. It does not say that this is a mutating operation affecting account balances, whether it requires specific permissions, whether it can be reversed (there is a delete_transfer sibling), or what happens on failure.

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 zero filler. It is efficient, though the terseness contributes to the coverage gaps noted elsewhere rather than being a structural flaw.

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?

A mutation tool with no annotations, no output schema, and a nested parameter object needs substantially more explanation than one sentence. An agent cannot tell from this definition what constraints apply to the two account references or what the call returns.

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?

Schema description coverage is 0% and the description adds no parameter meaning at all. The nested params object contains five fields (amount, txn_date, private_note, from_account_ref, to_account_ref) whose per-property descriptions are terse, and nothing in the description explains the source/destination account reference format or date conventions.

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 gives a specific verb and resource ('Create a bank transfer') plus the domain ('between accounts in QuickBooks Online'), which is enough to separate it from get_transfer/update_transfer/delete_transfer/search_transfers. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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?

There is no guidance on when to use this versus create_deposit, create_journal_entry, or create_payment, all of which could plausibly move money between accounts. No prerequisites are stated, such as both accounts needing to be bank-type accounts or sharing a currency.

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

Deploy Server