finance-reconcile-mcp

Find Firefly Duplicates

firefly_find_possible_duplicates

Read-onlyIdempotent

Identify possible duplicate transactions in Firefly III by comparing account, amount, date proximity, and description similarity.

Instructions

Find possible duplicate Firefly III transactions using same mapped account, amount, nearby date, and description similarity.

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

Input Schema

Name	Required	Description	Default
`days`	No
`account`	No
`end_date`	No
`start_date`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 29, 2026

TDQS

A3.5/5.0

Behavior5/5

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

The description goes beyond annotations by detailing the matching logic (account, amount, date, description similarity). Annotations indicate read-only, idempotent, non-destructive behavior, which aligns with 'find' semantics. No contradiction.

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 sentence with no unnecessary words. It efficiently conveys the core 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 having four parameters and no output schema, the description fails to explain parameter usage or return format. The tool has no required parameters, but the description doesn't clarify defaults or behavior with no arguments. This leaves significant gaps for an agent.

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?

Schema description coverage is 0%, so the description must explain parameters. It mentions 'amount' but no `amount` parameter exists. It does not clarify how `days`, `start_date`, `end_date`, or `account` relate to the matching criteria. This omission and misrepresentation makes the parameters poorly communicated.

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 finds possible duplicate Firefly III transactions and specifies the matching criteria: same mapped account, amount, nearby date, and description similarity. This distinguishes it from sibling tools like setup or reconciliation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it or which sibling tools might be more appropriate for related tasks.

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