Skip to main content
Glama
laf-rge

QuickBooks MCP

by laf-rge

edit_deposit

Modify an existing QuickBooks deposit—update date, memo, account, department, and lines. Lines merge with existing; include all line IDs to keep unchanged lines.

Instructions

Modify an existing deposit. Can update date, memo, deposit account, department, and/or lines. CRITICAL for line changes: The QB Deposit API does NOT replace lines - it merges them. Lines WITH line_id update existing lines. Lines WITHOUT line_id are ADDED as new. Lines NOT included are KEPT unchanged. To 'delete' a line, you must include ALL existing lines with their line_ids and set unwanted lines to amount: 0. Line amounts must sum to the original deposit total (use expected_total to override for corrupted deposits).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesDeposit ID to edit
txn_dateNoNew transaction date in YYYY-MM-DD format (optional)
memoNoNew private memo (optional)
deposit_to_accountNoNew deposit account name/number (Bank account)
department_nameNoHeader-level department/location name (auto-resolved to ID)
linesNoIMPORTANT: You MUST include ALL existing lines with their line_ids. Lines without line_id are ADDED (not replaced). Lines not included are KEPT (not deleted). To 'delete' a line, set its amount to 0. Line amounts must sum to original deposit total.
draftNoIf true, validate and show preview without saving (default: true)
expected_totalNoOverride total validation with this expected amount (for fixing corrupted deposits). Lines must sum to this value instead of current deposit total.
Behavior5/5

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

With no annotations, the description fully discloses the critical merge behavior of the QB Deposit API: lines are merged, not replaced. It explains how to delete lines by setting amount to 0 and the total validation, providing comprehensive behavioral transparency.

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 description is concise and front-loaded with the action, followed by important behavioral caveats. It could benefit from bullet points for readability, but it efficiently conveys critical information without unnecessary verbosity.

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

Completeness4/5

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

Given 8 parameters, 100% schema coverage, and no output schema or annotations, the description covers purpose, line merge behavior, total validation, and draft parameter. It is complete for a modification tool, though omitting return value description is acceptable without output schema.

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

Parameters4/5

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

Schema coverage is 100% with clear descriptions, but the tool description adds essential context beyond the schema, especially for the lines parameter and expected_total. It clarifies the merge logic and override scenario, which is not evident from schema alone.

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 description clearly states 'Modify an existing deposit' and lists the updatable fields (date, memo, deposit account, department, lines), distinguishing it from sibling tools like create_deposit and get_deposit.

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

Usage Guidelines4/5

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

The description gives explicit guidance on line handling: how to update, add, and delete lines, and when to use expected_total for corrupted deposits. It lacks explicit when-not-to-use but provides sufficient context for correct invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/laf-rge/quickbooks-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server