Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Delete Transaction

delete_transaction
DestructiveIdempotent

Permanently delete a Firefly III transaction group and all its splits by transaction ID. Use it to remove an entire transaction record and its linked entries in one action.

Instructions

Permanently delete a Firefly III transaction group (and all of its splits) by transaction ID.

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": "delete_transaction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe Firefly III transaction group ID to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description still adds real value by disclosing the destructive blast radius: the whole transaction group and every split are removed, not just a single entry. It does not mention authentication requirements or whether any confirmation/undo path exists, which keeps it short of a 5.

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?

One tightly written sentence with the destructive scope and the identifier front-loaded. Every clause earns its place and nothing is redundant.

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 one fully documented parameter, rich annotations, and no output schema, the description supplies the one thing structured fields cannot: that deletion cascades to all splits. It stops slightly short of complete by not addressing irreversibility or any prerequisite the agent should check before calling.

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 100% and the single parameter is already documented as 'The Firefly III transaction group ID to delete.' The description restates the same ID semantics without adding format, sourcing, or lookup guidance, so the baseline of 3 applies.

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 (delete) and a precisely scoped resource (a Firefly III transaction group and all of its splits) via a transaction ID. This clearly separates it from read/update siblings such as get_transaction and update_transaction, though it does not explicitly name any sibling as an alternative.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no precondition statement, and no mention of alternatives such as update_transaction or delete_account. The only signal is the word 'permanently', which hints at consequence but does not tell the agent when this tool is the right choice.

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