Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Get Financial Summary

get_financial_summary
Read-onlyIdempotent

Retrieve a Firefly III financial summary for a date range, including net worth, balance, earned, spent, bills, and left to spend. Filter by currency to compare key figures.

Instructions

Retrieve Firefly III's basic financial summary (net worth, balance, earned, spent, bills, left to spend) for a given date range.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "get_financial_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd date (YYYY-MM-DD), e.g. 2026-11-30
startYesStart date (YYYY-MM-DD), e.g. 2026-11-01
currency_codeNoOptional ISO 4217 currency code filter (e.g. CNY, USD, EUR)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 the safety profile is covered. The description adds the shape of what comes back (six named metrics), which is useful behavioral context, but says nothing about data scoping (per user vs. all), currency defaulting, or empty-range behavior.

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 parenthetical metric list earns its place by previewing the return payload in the absence of an output schema. Slightly dense but nothing to cut.

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 aggregate with a fully documented three-parameter schema and annotations, this is nearly complete; naming the returned metrics compensates for the missing output schema. Gaps are limited to currency default and scoping behavior.

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 formats and examples supplied for start and end and the ISO 4217 meaning of currency_code. The description only restates the date-range concept, adding no filtering semantics (e.g., inclusive bounds) or currency fallback behavior beyond the schema. 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?

The description names a specific verb (retrieve) and resource (basic financial summary) and enumerates the metrics returned (net worth, balance, earned, spent, bills, left to spend). This is unambiguous and clearly distinct from the account/transaction siblings, though it never explicitly contrasts itself with them.

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 only implied: the required date range and the word 'summary' suggest aggregating over a period rather than fetching individual records. There is no explicit statement of when to prefer this over list_transactions or search_transactions, 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.