Skip to main content
Glama
ninetails-io

gnucash-mcp

add_document_entry

Add a line item to a customer invoice, vendor bill, employee voucher, or credit note, with quantity, price, tax, and notes. Unposted documents only—unpost first to amend posted ones.

Instructions

Add a line item to a customer invoice, vendor bill, employee voucher, or credit note.

Only unposted documents accept entries — unpost_document first to amend a posted one. Amounts are decimal strings; the line total is quantity × price (plus tax when a taxtable is attached).

Args: document_type: "invoice", "bill", "voucher", or "credit_note". id: Document ID (e.g., "000001"). account: Income account for invoices / credit notes; expense account for bills and vouchers. Full path, %short GUID, or full GUID. description: Line item description. quantity: Quantity as a decimal string (e.g., "3"). price: Unit price as a decimal string (e.g., "125.00"). party_type: Credit notes only — disambiguates when a customer and vendor credit note share an ID. taxtable: Tax table name to apply. Optional. tax_included: Whether price already includes tax. notes: Optional entry notes. action: Optional entry action label (e.g., "Hours").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
notesNoOptional notes. Capped at 4096 characters at the MCP boundary; oversize input rejects with a clear error.
priceYes
actionNo
accountYes
quantityYes
taxtableNo
party_typeNo
descriptionYes
tax_includedNo
document_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Addedv1.4.4

TDQS

A4.8/5.0
Behavior5/5

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

The description discloses key behavioral details beyond the minimal annotations: decimal string amounts, line total calculation, tax behavior, and the unposted-document constraint. This materially helps the agent predict side effects and constraints.

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?

The description is well-organized with a clear opening, essential constraints, and a structured Args list. Despite covering 11 parameters, every sentence adds useful information without redundant restatement of the schema.

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?

For a mutation tool with 11 parameters, the description covers required inputs, optional inputs, edge cases, and prerequisite conditions. An output schema exists, so the lack of return-value detail is not a gap.

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?

With only 9% schema coverage, the description carries the full parameter burden and succeeds: every parameter is described, and high-value semantics are added, such as account direction by document type and party_type disambiguation for credit notes.

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 states a specific action ('Add a line item') and a specific resource (customer invoice, vendor bill, employee voucher, credit note). This clearly identifies what the tool does and differentiates it from siblings like create_document or create_transactions.

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?

It explicitly states when the tool applies ('Only unposted documents accept entries') and gives a prerequisite action (unpost_document first for posted documents). It does not explicitly contrast with alternatives like create_document, but the usage context is clear.

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

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/ninetails-io/gnucash-mcp'

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