Skip to main content
Glama
Firefly III MCP Server

Firefly III MCP Server

by edmondxie779

Get Account Details

get_account
Read-onlyIdempotent

Retrieve detailed attributes and current balance for a single Firefly III account by ID, with an optional date to calculate the balance for a specific day.

Instructions

Get detailed attributes and current balance for a single Firefly III account by its ID.

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": {
      "id": "<id>"
    },
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe Firefly III account ID.
dateNoOptional date (YYYY-MM-DD) on which to compute the account balance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so safety is covered. The description adds that the response includes attributes and a balance, which is useful context beyond the annotations, but it does not address error behavior for a missing or invalid ID or the effect of the date parameter on the balance.

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?

A single front-loaded sentence with the verb, resource, and scope in order and no filler. Every element earns its place.

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 two-parameter read tool with full schema coverage and rich annotations, the description covers what is returned at a high level. Only minor gaps remain around invalid-ID behavior and the date-to-balance relationship, which are not critical for correct invocation.

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 both parameters (id and the optional YYYY-MM-DD date) are already documented in the schema, establishing a baseline of 3. The description's phrase 'current balance' does not clarify that supplying date changes the balance computation point, so it adds little beyond the schema.

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 ('Get detailed attributes and current balance') plus a scope constraint ('a single Firefly III account by its ID'), which distinguishes it from list_accounts and search_accounts without naming them. It stops short of explicit sibling differentiation, so a 4 rather than a 5.

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: 'by its ID' suggests the caller already has an account ID, presumably from list_accounts or search_accounts. There is no explicit statement of when to prefer this over those alternatives or what to do when the ID is unknown.

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