Skip to main content
Glama
duganth

py-ynab-mcp

by duganth

create_transaction

Record a transaction in YNAB by providing account, dollar amount, and date, and optionally set payee, category, memo, cleared status, or approval.

Instructions

Create a transaction in YNAB.

Args: account_id: Account UUID. amount: Dollar amount ("-42.50" for outflow, "100.00" for inflow). date: Transaction date (YYYY-MM-DD). payee_name: Payee name (YNAB auto-creates new payees). category_id: Category UUID. memo: Transaction memo. cleared: "cleared", "uncleared", or "reconciled". approved: Whether the transaction is approved. budget_id: Budget ID. Defaults to last-used budget. dry_run: Validate and preview without creating.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
memoNo
amountYes
clearedNo
dry_runNo
approvedNo
budget_idNo
account_idYes
payee_nameNo
category_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the burden. It explains key behaviors: amount sign convention, date format, auto-creation of payee via payee_name, and dry_run for preview. It lacks details on error handling, idempotency, or return value, but the output schema may cover the latter.

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 starts with a clear purpose followed by a well-structured bullet-like list of parameters. It is fairly concise given the number of parameters (10), though some lines could be shortened. No wasted sentences.

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 complexity of 10 parameters and no annotations, the description covers all parameter semantics and flags key behavior (auto-created payee, dry_run). It does not mention possible errors, rate limits, or response format, but the existence of an output schema mitigates the last point. Overall, it is quite complete.

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?

The description adds significant meaning beyond the input schema, which has no descriptions. It explains each parameter with examples and defaults, such as amount format, date format, payee auto-creation, and dry_run purpose. This fully compensates for the 0% schema description coverage.

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 'Create a transaction in YNAB,' which is a specific verb+resource. It distinguishes from sibling tools like create_scheduled_transaction and create_transactions by focusing on a single immediate transaction.

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 lists all parameters with explanations, including dry_run for validation. However, it does not explicitly state when to use this tool versus alternatives like create_transactions, though the distinction is implied by the name and parameter differences.

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/duganth/py-ynab-mcp'

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