Skip to main content
Glama
laf-rge

QuickBooks MCP

by laf-rge

create_expense

Create an expense in QuickBooks by specifying payment type, account, payee, and line items. Automatically looks up account, vendor, and department names to assign IDs.

Instructions

Create an expense (Purchase). Accepts account/department/vendor names (will lookup IDs automatically). Covers Cash, Check, and Credit Card payment types. Note: PaymentType cannot be changed after creation. DepartmentRef is header-level only. Returns expense details and a link to view in QuickBooks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payment_typeYesPayment method: 'Cash', 'Check', or 'CreditCard'. Cannot be changed after creation.
payment_accountYesBank or credit card account name or number (e.g., 'PLAT BUS CHECKING', '5752'). Will be looked up to get ID.
txn_dateYesTransaction date in YYYY-MM-DD format
entity_nameNoPayee/vendor display name (e.g., 'Simplisafe', 'PG&E'). Will be looked up to get ID.
entity_idNoPayee/vendor ID (use if you already know it, otherwise use entity_name)
department_nameNoHeader-level department/location name (e.g., '20358', 'Cotati'). Will be looked up to get ID.
department_idNoHeader-level department/location ID (use if you already know it, otherwise use department_name)
memoNoPrivate memo for the expense
doc_numberNoReference number for the expense (optional)
linesYesArray of expense line items. Provide account_name OR account_id (name preferred).
draftNoIf true, validate and show preview without creating (default: true)
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses immutability of payment_type, that department is header-level only, auto-lookup of IDs, and returns expense details with a link to QuickBooks. No contradictory information.

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?

Five sentences, each adding distinct information. No redundant or filler content. Front-loaded with primary purpose. Very concise and well-structured.

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

Completeness5/5

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

Given 11 parameters and no output schema, the description covers the general flow, key constraints, auto-lookup behavior, draft mode, and return value (details + link). Sufficient for an agent to use the tool correctly.

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

Parameters5/5

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

Schema description coverage is 100%, but description adds significant value: explains auto-lookup behavior for names, confirms immutability of payment_type, and clarifies that department is header-level. Example placeholders like 'Simplisafe' and 'PLAT BUS CHECKING' help the agent.

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?

Starts with 'Create an expense (Purchase)' – clear verb+resource. Distinguishes from siblings like create_bill, create_deposit by specifying accepted payment types (Cash, Check, CreditCard) and providing a sample description.

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?

Provides context: accepts names for lookup, covers three payment types, notes that PaymentType cannot be changed after creation, and DepartmentRef is header-level only. However, it does not explicitly differentiate from alternatives like create_bill, which may be used for similar purposes.

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