Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

List Account Transactions

list_account_transactions
Read-onlyIdempotent

Retrieve transactions for a Firefly III account and filter them by date range or transaction type to review spending, income, and transfers.

Instructions

List transactions associated with a specific Firefly III account ID, optionally filtered by date range and transaction type.

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": {
      "account_id": "<account_id>"
    },
    "name": "list_account_transactions"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoEnd date (YYYY-MM-DD).
pageNoPage number.
typeNoOptional transaction type filter.
limitNoItems per page.
startNoStart date (YYYY-MM-DD).
account_idYesThe Firefly III account ID.

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, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds no further behavioral context such as result ordering, pagination defaults, or what happens when the account ID does not exist — useful but not essential given the annotation coverage.

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?

A single front-loaded sentence with no filler; the core action and scope come first and the optional filters follow. Slightly wordy in the account-ID clause, but nothing extraneous.

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?

With six parameters all documented in the schema and no output schema, the definition covers the essentials for invocation. It leaves gaps around pagination behavior and result contents that matter for a paged list endpoint but are not strictly required to call it.

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%, so account_id, start/end, type, page and limit are already fully documented in the schema. The description names the date-range and type filters but adds no syntax, defaults, or constraints (e.g., max 200 per page) beyond what the schema provides, making baseline 3 correct.

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 (list transactions) plus the scoping qualifier 'associated with a specific Firefly III account ID', which separates it from the broader list_transactions. It stops short of naming that sibling explicitly, so differentiation requires the agent to infer from the scope phrase.

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?

'optionally filtered by date range and transaction type' implies the filtering use case, but there is no explicit when-to-use vs. list_transactions or search_transactions, and no stated exclusions. Usage is inferable but not spelled out.

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