Skip to main content
Glama

ynab_create_receipt_split_transaction

Create a split transaction from itemized receipt data, automatically allocating tax proportionally across categories.

Instructions

Create a split transaction from itemized receipt data with proportional tax allocation.

Args:

  • budget_id (string, optional): Budget UUID. Omit to use the default budget.

  • account_id (string, required): Account UUID.

  • payee_name (string, required): Store/payee name.

  • receipt_total (number, required): Total amount in dollars (positive).

  • receipt_tax (number, required): Tax amount in dollars (0 if none).

  • categories (array, required): Category groups with items. Each item needs name, amount.

  • date (string, optional): ISO date. Default: today.

  • memo (string, optional): Memo applied to the parent transaction.

  • receipt_subtotal (number, optional): Pre-tax subtotal for validation.

  • cleared (string, optional): "cleared", "uncleared", or "reconciled". Default: "uncleared".

  • approved (boolean, optional): Mark as approved. Default: false.

  • flag_color (string, optional): Transaction flag color ("red", "orange", "yellow", "green", "blue", "purple").

  • dry_run (boolean, optional): Preview subtransactions without saving. Default: false.

Use this helper when you have receipt line items and want tax allocated across categories automatically. For generic manual split transactions without receipt/tax logic, use "ynab_create_transaction" with "subtransactions".

Returns: transaction with subtransactions and receipt_summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_idNo
account_idYes
payee_nameYes
dateNo
memoNo
receipt_subtotalNo
receipt_taxYes
receipt_totalYes
categoriesYes
clearedNo
approvedNo
flag_colorNo
dry_runNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Discloses behavior: creates transaction, proportional tax allocation, dry_run preview, and return value. Consistent with annotations (readOnlyHint=false). No contradictions.

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?

Concise with clear bullet-point parameter listing, front-loaded purpose, and no unnecessary information.

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?

Complex tool with 13 params and nested categories, but description covers all essential aspects: behavior, parameter details, usage context, return value. Output schema exists so return details suffice.

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?

Despite 0% schema description coverage, the description provides detailed explanations for all 13 parameters, adding meaning beyond the schema.

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 it creates a split transaction from receipt data with proportional tax allocation. It is distinct from sibling tools like ynab_create_transaction for generic splits.

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

Usage Guidelines5/5

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

Explicitly says when to use (receipt line items with tax allocation) and when not to, and provides alternative ynab_create_transaction with subtransactions.

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/dizzlkheinz/ynab-mcpb'

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