Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

List Transactions

list_transactions
Read-onlyIdempotent

Retrieve Firefly III transactions filtered by date range or transaction type to review spending, income, and transfers.

Instructions

List Firefly III transactions with optional date range ('start', 'end' in YYYY-MM-DD) and transaction type filter ('withdrawal', 'deposit', 'transfer', or 'all').

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

Input Schema

NameRequiredDescriptionDefault
endNoEnd date inclusive (YYYY-MM-DD).
pageNoPage number (starts at 1).
typeNoTransaction type filter (defaults to 'all').all
limitNoTransactions per page.
startNoStart date inclusive (YYYY-MM-DD).

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, openWorldHint and destructiveHint=false, so the safety profile is covered structurally. The description adds only the filtering semantics and says nothing about pagination behavior, default page size, ordering of results, or what the response contains — notable gaps for a list endpoint that is paginated in the schema.

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 format hint and type filter are attached directly to their parameters. Slightly dense with parentheticals, and the type list is incomplete relative to the enum, but nothing is wasted.

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 no output schema, the description carries some burden for explaining what comes back, and it is silent on result shape, pagination defaults, and result ordering. It is adequate for a simple read-only lister with full schema coverage, but not complete for an agent needing to page through results correctly.

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%, so all five parameters are already documented, including the page/limit pagination pair and the full type enum. The description restates 'start'/'end' format and a subset of the type values, adding no meaning beyond the schema — 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 ('List Firefly III transactions') plus the two filter dimensions it supports, so the agent knows exactly what it retrieves. It does not distinguish itself from siblings such as search_transactions or list_account_transactions, so an agent cannot tell from this text alone which lister to pick.

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 through the optional filter framing ('optional date range', 'transaction type filter'), which hints at when this tool is appropriate. There is no explicit when-to-use guidance, no mention of how it differs from search_transactions or list_account_transactions, and no stated prerequisites or exclusions.

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