Skip to main content
Glama
chadlis

ynab-mcp

by chadlis

Create a transaction

ynab_create_transaction

Add a transaction to a YNAB account by specifying amount, date, payee, and category. Negative amounts record expenses, positive amounts record income.

Instructions

Create a transaction in an account.

The amount is given in normal currency units (e.g. -12.50 for a 12.50 expense); conversion to milliunits is automatic. Returns the new id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memoNoFree-form memo
amountYesAmount in currency units. NEGATIVE for an expense, positive for income. E.g. -12.50
clearedNo'cleared', 'uncleared' or 'reconciled'uncleared
approvedNoMark as approved
txn_dateNoDate YYYY-MM-DD (default: today)
budget_idNoBudget id, or 'last-used'last-used
account_idYesTarget account (required)
payee_nameNoPayee name (created if it does not exist)
category_idNoCategory to assign

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses that amount conversion to milliunits is automatic and that the new id is returned, adding value beyond annotations. No contradictions with annotations.

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?

Two sentences cover the core action and key behavior (conversion, return value), but could be more structured with bullet points for readability.

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 output schema exists and the description mentions the returned id, it is fairly complete. However, it does not mention other potential response fields or error conditions.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds useful context about amount units and conversion, which aids correct usage beyond the schema descriptions.

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 action ('Create') and the resource ('a transaction in an account'), which is specific and distinguishes it from sibling tools like 'list' or 'update'.

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

Usage Guidelines3/5

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

While the purpose is clear, the description does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context like needing account_id.

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

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