Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

List Accounts

list_accounts
Read-onlyIdempotent

Retrieves Firefly III accounts and balances, filtered by account type and optional date, so you can locate assets, expenses, revenue, or liabilities.

Instructions

List Firefly III accounts and their balances. Filter by account type (e.g. 'asset' for bank/checking/savings/credit cards, 'expense' for merchants, 'revenue' for income sources, 'liability' for loans/debts).

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional date (YYYY-MM-DD) on which to compute account balances. Defaults to today.
pageNoPage number for pagination (starts at 1).
typeNoAccount type filter. Defaults to 'asset' (your own bank/cash/card accounts). Use 'all' to return every account type.asset
limitNoMaximum number of accounts per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description has a lower burden. The description adds that balances are returned and explains account type meanings, but does not describe pagination, balance-date behavior, or other operational details.

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?

The description is two sentences, front-loads the purpose, and uses the second sentence efficiently for filter semantics. There is no filler or redundant wording.

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 simple read-only list tool with four optional, fully documented parameters, the description covers purpose and key filtering semantics adequately. It could be slightly more complete by differentiating from search_accounts, but no critical invocation detail is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameter basics are already documented. The description adds useful semantic meaning for account types, mapping 'asset', 'expense', 'revenue', and 'liability' to real-world account categories beyond the enum values alone.

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 and resource: listing Firefly III accounts and their balances. It is clear enough to distinguish from mutation tools, but it does not differentiate itself from the sibling search_accounts tool.

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?

It implies usage for listing accounts and explains how to filter by account type. However, it gives no explicit when-to-use versus search_accounts or get_account guidance, and no exclusions or prerequisites.

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