finance-reconcile-mcp

List Firefly Accounts

setup_list_firefly_accounts

Read-onlyIdempotent

Lists Firefly III asset and liability accounts to create an account-map.json for reconciliation.

Instructions

List Firefly III asset/liability accounts for building account-map.json.

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

Input Schema

Name	Required	Description	Default
`type`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 29, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to repeat safety aspects. It adds context about the use case but does not disclose other behavioral traits like pagination or output format.

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 a single, concise sentence with no unnecessary words. It is front-loaded and efficiently communicates the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite annotations covering safety, the description lacks crucial details: the meaning and allowed values of the type parameter, and the output format. For a tool with one undocumented parameter and no output schema, this is insufficient.

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

Parameters1/5

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

The schema has one parameter (type) with 0% description coverage and no enum values. The description does not mention the parameter or its allowed values, leaving the agent without guidance on how to use it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists Firefly III asset/liability accounts for building account-map.json. It uses a specific verb (list) and resource (accounts) and distinguishes from sibling tools like setup_list_simplefin_accounts.

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?

The description mentions the purpose ('for building account-map.json'), implying when to use it, but does not provide explicit guidance on when not to use or how it compares to alternatives like setup_list_simplefin_accounts.

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