Skip to main content
Glama
przbadu

Firefly III MCP Server

by przbadu

Create Firefly III Transaction

firefly_create_transaction

Create transactions in Firefly III to record expenses, income, and transfers. Logs withdrawals, deposits, and account transfers with automatic account creation and support for split transactions, categories, and budgets.

Instructions

Create a new transaction in Firefly III.

Supports withdrawals (expenses), deposits (income), and transfers between accounts.

For a withdrawal: provide source_name (your asset account, e.g. "Checking Account") and destination_name (the expense account, e.g. "Supermarket"). For a deposit: provide source_name (revenue account, e.g. "Employer") and destination_name (your asset account). For a transfer: both source and destination should be your own asset accounts.

If an expense/revenue account doesn't exist yet, Firefly III will auto-create it.

Returns: The created transaction with its ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesTransaction type
descriptionYesMain transaction description
dateYesTransaction date in YYYY-MM-DD format
amountYesTransaction amount as a string, e.g. '25.50'
source_nameNoSource account name (required for withdrawals/transfers)
source_idNoSource account ID (alternative to source_name)
destination_nameNoDestination account name (required for deposits/transfers). For withdrawals this is the expense account (e.g. 'Grocery Store').
destination_idNoDestination account ID (alternative to destination_name)
category_nameNoCategory name (e.g. 'Groceries')
budget_nameNoBudget name
tagsNoTags to attach
notesNoAdditional notes
currency_codeNoCurrency code, e.g. 'USD', 'EUR'. Defaults to account default.
splitsNoFor split transactions, provide multiple splits instead of top-level amount/source/destination
Behavior4/5

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

Adds valuable behavioral context beyond annotations: explicitly states that Firefly III auto-creates expense/revenue accounts if missing, and documents the return value ('The created transaction with its ID') since no output schema exists. Deducting one point because it doesn't address idempotency (idempotentHint=false) or error scenarios.

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?

Perfectly structured and front-loaded: starts with the core action, follows with three parallel examples for transaction types, then auto-creation note, then return value. Every sentence conveys distinct, high-value information with zero redundancy.

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 (14 params including nested splits objects) and lack of output schema, the description covers the primary use cases comprehensively. Minor deduction for not mentioning 'reconciliation' or 'opening-balance' types from the enum, and not explaining the splits parameter usage (though schema coverage compensates for the latter).

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?

While the schema has 100% coverage (baseline 3), the description adds crucial semantic relationships not evident in the schema: it explains that source_name for withdrawals should be 'your asset account' while destination_name should be 'the expense account', clarifying the domain logic for how these parameters interact based on transaction type.

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 opens with a specific verb+resource ('Create a new transaction in Firefly III') and immediately distinguishes this tool from sibling account/budget/category creation tools by detailing the three specific transaction types supported: withdrawals, deposits, and transfers.

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?

Provides explicit when-to-use guidance for each transaction type with concrete parameter mappings: 'For a withdrawal: provide source_name... and destination_name...', 'For a deposit: provide source_name...', etc. Also notes the auto-creation behavior for missing accounts, which helps agents understand prerequisites.

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/przbadu/firefly-iii-mcp-server'

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