Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Update Transaction

update_transaction
Idempotent

Update an existing Firefly III transaction group by ID, including group title and split details. For multi-split transactions, provide each split’s transaction_journal_id to modify the correct entry.

Instructions

Update an existing Firefly III transaction group by ID. When updating a multi-split transaction, pass 'transaction_journal_id' inside each split (retrieve them first with 'get_transaction').

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_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe Firefly III transaction group ID to update.
apply_rulesNoWhether to re-apply Firefly III rules.
group_titleNoUpdated group title (or null to clear).
transactionsNoUpdated split fields.
fire_webhooksNoWhether to trigger webhooks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, openWorld=true, destructive=false, so the safety and repeatability profile is covered. The description adds useful split-handling behavior but does not say whether this is a partial or full replacement update, whether omitted fields are cleared, or what happens when apply_rules/fire_webhooks fire. For a mutation tool, the patch-vs-replace semantics are a notable undisclosed behavior.

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?

Two sentences, zero filler, with the core action stated first and the multi-split caveat second. Every clause carries actionable information and nothing is repeated from the schema.

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?

With no output schema, an agent still gets enough to call the tool: target ID, split-array requirement, and the journal-ID lookup path. The missing piece is update semantics (partial vs. full replacement) and the return shape, which matters for a nested-array mutation. Given full schema coverage and rich annotations, this is close to complete.

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 description coverage is 100%, so the baseline would be 3. The description earns a bump by surfacing the one genuinely non-obvious parameter, 'transaction_journal_id', and explaining both its conditional requirement and how to obtain the value. It adds no meaning for apply_rules, fire_webhooks, or group_title beyond what the schema already states.

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 opens with a specific verb+resource: 'Update an existing Firefly III transaction group by ID', which cleanly separates it from create_transaction, delete_transaction, and the read-only get_transaction. It also distinguishes the group-level object from individual split journals. It stops short of explicitly naming a sibling it supersedes, so a 4 rather than a 5.

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?

It gives concrete when-to-do guidance for the hard case: when updating a multi-split transaction, pass 'transaction_journal_id' inside each split and retrieve those IDs first with 'get_transaction'. That is a real workflow prerequisite naming an alternative tool. There is no when-not-to-use guidance (e.g. when to prefer create/delete or what to do if the ID doesn't exist), so it falls short of a 5.

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