finance-reconcile-mcp

Suggest Account Map

setup_suggest_account_map

Read-onlyIdempotent

Fetch SimpleFIN and Firefly III accounts to generate a suggested account mapping draft for reconciliation.

Instructions

Fetch SimpleFIN and Firefly III accounts and return a suggested account-map.json draft. Does not write files.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 29, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate idempotent and read-only behavior; description adds that it fetches accounts and returns a draft, reinforcing the non-destructive nature. No contradictions.

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?

Two brief sentences, front-loaded with the main action, and immediately clarifies it does not write files. No unnecessary words.

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

Completeness3/5

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

Adequate for a simple tool with no input and clear action, but lacks details about the output format or how the draft is structured. Could benefit from mentioning it uses stored configs.

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 coverage is 100% (no parameters), so baseline is 3. Description adds no parameter information since none exist, but could have explained why no input is needed.

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?

Description clearly states it fetches accounts from two specific sources (SimpleFIN and Firefly III) and returns a draft map. Distinguishes from siblings like setup_validate_account_map and setup_save_account_map which have different verbs.

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 says 'Does not write files' which implies read-only usage, but does not explicitly state when to use this tool over alternatives like setup_validate_account_map or setup_save_account_map. Context from sibling tool names suggests a sequence, but not stated.

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