Firefly III MCP Server

List Firefly III Transactions

firefly_list_transactions

Read-onlyIdempotent

List and filter Firefly III transactions by type, date range, and page. Retrieve withdrawal, deposit, and transfer records to track spending patterns and review financial history.

Instructions

List transactions from Firefly III with optional filters.

Supports filtering by type (withdrawal, deposit, transfer), date range, and pagination. Returns a paginated list of transactions with key details.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "firefly_list_transactions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max results to return
`page`	No	Page number (1-based)
`type`	No	Filter by transaction type
`start`	No	Start date filter (YYYY-MM-DD)
`end`	No	End date filter (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Apr 7, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, covering safety and behavioral traits. Description adds value by specifying pagination behavior and listing supported filter types, but does not elaborate on rate limits, auth requirements, or what 'key details' means in the return value.

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?

Three efficiently structured sentences: purpose statement, capability enumeration, and return description. Zero redundancy—every sentence conveys distinct information not duplicated in structured fields.

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?

Given 100% schema coverage and comprehensive annotations, the description is adequate. It acknowledges the paginated nature of returns, which is crucial since no output schema exists. Could improve by clarifying what 'key details' includes or explicitly noting all parameters are optional.

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 description coverage is 100%, with all 5 parameters (limit, page, type, start, end) fully documented. Description mentions the filter categories exist but does not add semantic depth, syntax examples, or constraints beyond what the schema already provides.

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?

Clearly states 'List transactions from Firefly III' with specific verb and resource. Mentions filtering capabilities (type, date range, pagination) but does not distinguish from sibling firefly_search_transactions, which likely performs text search versus this tool's structured filtering.

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?

Provides no guidance on when to use this tool versus alternatives like firefly_search_transactions (text search) or firefly_get_transaction (single record retrieval). Does not mention prerequisites or when not to use.

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