Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Create Account

create_account

Add a new Firefly III account for assets, expenses, revenue, liabilities, or cash, including optional account roles and liability details.

Instructions

Create a new account in Firefly III. For 'asset' accounts, 'account_role' defaults to 'defaultAsset' (if 'ccAsset', also pass 'credit_card_type' and 'monthly_payment_date'). For 'liability' accounts, 'liability_type' ('loan', 'debt', or 'mortgage') is required.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "type": "<type>"
    },
    "name": "create_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
bicNoBIC/SWIFT code if applicable.
ibanNoIBAN if applicable.
nameYesAccount name (must be unique per account type).
typeYesType of account to create.
notesNoOptional Markdown notes for the account.
activeNoWhether the account is active.
interestNoInterest rate percentage for liabilities (e.g. '4.25').
account_roleNoRole for 'asset' accounts only: 'defaultAsset', 'sharedAsset', 'savingAsset', 'ccAsset' (credit card), or 'cashWalletAsset'. Defaults to 'defaultAsset' when type='asset'.
currency_codeNoISO 4217 currency code (e.g. CNY, USD, EUR). Defaults to Firefly III's primary currency.
account_numberNoBank or card account number.
liability_typeNoRequired when type='liability': 'loan', 'debt', or 'mortgage'.
interest_periodNoInterest period for liabilities.
opening_balanceNoInitial opening balance as a decimal string (e.g. '1000.00'). Requires 'opening_balance_date' when set.
virtual_balanceNoVirtual balance buffer as a decimal string (e.g. '0.00').
credit_card_typeNoRequired when account_role='ccAsset'. Currently Firefly III supports 'monthlyFull'.
include_net_worthNoWhether to include this account in net worth calculations.
liability_directionNoDirection when type='liability': 'debit' (you owe money) or 'credit' (you are owed money).
monthly_payment_dateNoRequired when account_role='ccAsset' (YYYY-MM-DD).
opening_balance_dateNoDate of the opening balance (YYYY-MM-DD). Required if 'opening_balance' is provided.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive, non-idempotent, open-world operation, so the description carries a lighter burden. The description adds conditional field requirements for asset and liability accounts but says nothing about failure behavior (e.g., duplicate names, which the schema notes must be unique per type), validation errors, or what the call returns.

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 tightly packed sentences, front-loaded with the core action followed by type-specific rules. There is no filler, though the second half largely re-serializes conditions already present in the field descriptions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 19-parameter creation tool with no output schema and no nested objects, the description covers only the two conditional branches and omits what a caller gets back (e.g., the new account ID) or how unique-name conflicts surface. The rich schema compensates for most parameter gaps, leaving this adequate but not complete.

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

Parameters3/5

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

With 100% schema description coverage, the schema already documents every one of the 19 parameters, including the ccAsset and liability conditionals. The description restates the same conditional dependencies ('credit_card_type' and 'monthly_payment_date' for ccAsset, 'liability_type' for liability) and the defaultAsset default, so it adds little beyond what the schema provides; baseline 3 applies.

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 and resource ("Create a new account in Firefly III"), which is unambiguous and easy to distinguish from siblings like create_transaction, update_account, or get_account. An agent can tell immediately that this tool creates a single account rather than modifying or listing one.

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?

Usage guidance is implied rather than stated: nothing explains when to choose this over update_account or what prerequisites exist before calling it. The conditional rules about account_role and liability_type are useful but function more as field-level constraints than selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.