Skip to main content
Glama
laf-rge

QuickBooks MCP

by laf-rge

edit_sales_receipt

Modify an existing sales receipt by updating date, memo, deposit account, department, or lines. Add, update, or delete line items.

Instructions

Modify an existing sales receipt. Can update date, memo, deposit account, department, and/or lines. For lines: provide line_id to update existing line, omit line_id to add new line (requires item_name), set delete=true to remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSales receipt 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)
linesNoLine modifications. Provide line_id to update existing line, omit to add new line.
draftNoIf true, validate and show preview without saving (default: true)
Behavior4/5

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

No annotations provided, but description covers line edit/add/delete logic and draft mode. Lacks info on idempotency, error handling, or full side effects, but adequate for mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficient sentences: general purpose then line details. No fluff, key information front-loaded.

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?

Covers main modifications adequately. Missing return value description and error conditions, but overall complete for a moderate-complexity tool with no 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%. Description adds value by explaining line modification semantics (line_id, delete=true) and auto-resolution of item_name, going beyond schema descriptions.

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?

Description clearly states 'Modify an existing sales receipt' with specific fields (date, memo, deposit account, department, lines), distinguishing it from create and other edit tools.

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?

No explicit when-to-use or alternatives mentioned. Usage is implied by 'modify existing' but lacks guidance on choosing between edit and create or other edit tools.

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