Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Delete Account

delete_account
DestructiveIdempotent

Permanently deletes a Firefly III account by ID; transactions exclusively linked to it may also be affected or deleted.

Instructions

Permanently delete a Firefly III account by ID. Warning: deleting an account may also affect or delete transactions exclusively linked to it.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe Firefly III account ID to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so safety basics are covered. The description adds genuinely new behavioral context that the annotations do not carry: the operation is permanent and may cascade to transactions exclusively linked to the account, which is exactly the kind of side effect an agent needs before calling a destructive tool.

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 short sentences with the action first and the risk warning second - nothing redundant, and the most important caution is not buried.

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?

For a one-parameter destructive delete with full annotation coverage, the description covers the action, permanence, and the main cascade risk. It omits failure conditions and authorization requirements, but those are minor gaps at this complexity level.

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% for the single parameter and the schema already documents it as "The Firefly III account ID to delete." The description says only "by ID," adding no format, validation, or lookup guidance beyond the schema, so the baseline 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?

States a specific verb and resource: "Permanently delete a Firefly III account by ID." The resource (account) naturally separates it from the transaction-oriented siblings, though no sibling is named explicitly.

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 is implied rather than stated - an agent can infer this is for removing an account, and the warning hints that caution is needed when transactions exist. There is no explicit statement of when to prefer update_account over deletion, or any preconditions such as account balance being zero.

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