Skip to main content
Glama

ynab_reconcile_account

Idempotent

Reconcile a YNAB account by matching bank statement CSV transactions, detecting discrepancies, and optionally auto-creating, updating clearing status, or un-clearing transactions.

Instructions

Guided account reconciliation: match bank CSV transactions to YNAB, detect discrepancies, and optionally execute bulk create/update/unclear operations.

Args:

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

  • account_id (string, required): Account UUID to reconcile.

  • csv_file_path or csv_data (string, required): Bank export file path or inline CSV text.

  • statement_balance (number, required): Ending balance from the bank statement (dollars). For credit cards and other liability accounts, pass a negative value (e.g. -6143.27 means you owe $6,143.27).

  • statement_end_date (string, optional): Statement closing date (YYYY-MM-DD). Filters CSV and triggers balance verification. Auto-detected from CSV if omitted.

  • match_strictness (string, optional): Matching sensitivity — "loose" (more matches), "normal" (default), or "strict" (fewer false positives).

  • sign_convention (string, optional): How to treat CSV amount signs — "auto" (default, detects from data), "invert" (negate all amounts), "as_is" (use amounts unchanged). Useful when auto-detection fails for liability accounts.

  • dry_run (boolean, optional): Preview actions without executing. Default: true.

  • auto_create_transactions (boolean, optional): Auto-create missing transactions. Default: false.

  • auto_update_cleared_status (boolean, optional): Auto-mark matched transactions as cleared. Default: false.

  • auto_unclear_missing (boolean, optional): Auto-mark statement-missing cleared transactions as uncleared when reconciliation remains unbalanced. Default: false.

  • max_suggestions_in_output (number, optional): Limit unmatched items and suggestions shown in the human report. Default: 20.

Returns: human-readable reconciliation narrative + structured JSON (unmatched_bank, unmatched_ynab, suggestions, execution_summary when actions are performed).

Examples:

  • Preview reconciliation: set dry_run=true (default)

  • Execute: set dry_run=false and explicitly enable the write flags you want, e.g. auto_update_cleared_status=true

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
budget_idNo
account_idYes
csv_file_pathNo
csv_dataNo
csv_formatNo
statement_balanceYes
statement_end_dateNo
date_tolerance_daysNo
match_strictnessNonormal
auto_create_transactionsNo
auto_update_cleared_statusNo
auto_unclear_missingNo
auto_adjust_datesNo
dry_runNo
sign_conventionNoauto
max_suggestions_in_outputNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
humanYes
structuredYes
Behavior4/5

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

Annotations indicate idempotentHint=true, and the description reinforces this by highlighting dry_run default and explicit write flags. It also discloses nuanced behaviors like sign_convention for liability accounts and auto_unclear_missing. No contradictions with annotations detected.

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 well-structured with clear sections (summary, Args, Returns, Examples) and is front-loaded. While comprehensive, it could be slightly shorter by removing redundant phrasing, but overall it's efficient for the complexity.

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 the tool's complexity (16 parameters, nested csv_format, output structure), the description covers core functionality, return format, and usage patterns thoroughly. Minor gaps: no mention of error handling or rate limits, but output schema existence compensates.

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 tool description provides exhaustive meaning for all 16 parameters, including practical guidance on statement_balance sign, match_strictness options, sign_convention, and auto-flags. This adds significant value beyond the minimal 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 the tool performs 'guided account reconciliation' by matching CSV transactions to YNAB, detecting discrepancies, and optionally writing changes. This verb-resource combination distinguishes it from siblings like ynab_create_transactions which do not offer reconciliation logic.

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 provides explicit usage context, including examples for dry-run vs. execution and parameter defaults. However, it does not mention when NOT to use this tool (e.g., if simpler import is needed) or compare to alternatives like ynab_compare_transactions or ynab_create_transactions.

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