Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Update Account

update_account
Idempotent

Modifies an existing Firefly III account by ID, changing only the fields you provide while preserving the current name when omitted. Use it to update balances, account details, role, currency, or status.

Instructions

Update an existing Firefly III account by ID. Only fields you pass will be modified (if 'name' is omitted, the existing account name is preserved automatically).

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": {
      "id": "<id>"
    },
    "name": "update_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe Firefly III account ID to update.
bicNoUpdated BIC (or null to clear).
ibanNoUpdated IBAN (or null to clear).
nameNoNew account name.
notesNoUpdated notes (or null to clear).
activeNoWhether the account is active.
interestNo
account_roleNoAccount role (for asset accounts).
currency_codeNoISO 4217 currency code.
account_numberNoUpdated account number (or null to clear).
liability_typeNo
interest_periodNo
opening_balanceNoUpdated opening balance.
virtual_balanceNoUpdated virtual balance.
credit_card_typeNo
include_net_worthNoWhether to include in net worth.
monthly_payment_dateNo
opening_balance_dateNoUpdated opening balance date (YYYY-MM-DD).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's partial-update clarification ('if name is omitted, the existing name is preserved') adds genuine value beyond that, but it says nothing about permissions, what happens when a field like currency_code is changed on an account with existing transactions, or error behavior for an unknown ID.

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 short sentences with no filler, and the partial-update rule is placed immediately after the purpose statement. The parenthetical example is slightly redundant with its own preceding clause, keeping it just below 5.

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 an 18-parameter mutation tool with no output schema, the definition covers identity and patch semantics but leaves return shape, failure modes, and field-interaction side effects unaddressed. It is enough to call the tool correctly on simple field updates, but thin for complex ones such as changing account_role or currency_code.

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?

Schema coverage is 72%, so most of the 18 parameters already carry their own descriptions. The description mentions only 'name' and uses it to illustrate omission semantics rather than to explain the field; it adds no meaning for the enum-constrained parameters (account_role, liability_type, credit_card_type, interest_period) or the date-patterned fields. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Update an existing Firefly III account by ID'), which clearly separates it from create_account, delete_account, and get_account. It stops short of naming a sibling or scope boundary explicitly, so the differentiation comes from the resource noun alone rather than deliberate routing guidance.

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?

The line 'Only fields you pass will be modified' establishes patch-style usage, which is real guidance about how to call it. There is no statement of prerequisites (the account must already exist), no when-not-to-use case, and no pointer to delete_account or create_account for the adjacent operations.

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