finance-reconcile-mcp

Save Account Map

setup_save_account_map

Idempotent

Writes account-map.json to the local path to configure account mapping for reconciliation. This only updates local config, never mutates external systems.

Instructions

Write account-map.json to the configured local account mapping path. This only writes local config and never mutates Firefly III or SimpleFIN.

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": {
      "confirm_write": "<confirm_write>"
    },
    "name": "setup_save_account_map"
  }
}

Input Schema

Name	Required	Description	Default
`overwrite`	No
`account_map`	No
`confirm_write`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 29, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds value by confirming the write is local-only and does not affect external systems, providing useful context beyond the annotations.

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 two sentences long, front-loaded with the action, and every sentence contributes meaning without redundancy.

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 reasonable annotations, the description fails to explain the parameters or what the tool expects as input. For a tool with 3 parameters including a required confirm_write and an undefined account_map, this is a significant gap that leaves the agent underinformed.

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%, and the description provides no information about the three parameters (overwrite, account_map, confirm_write). The agent cannot determine their purpose or required format, especially for the undefined account_map object.

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 writes account-map.json to a local path, with a specific verb and resource. This distinguishes it from sibling tools like setup_suggest_account_map and setup_validate_account_map, which perform different actions.

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

Usage Guidelines4/5

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

The description explains that the tool only writes local config and never mutates Firefly III or SimpleFIN, providing clear boundary context. While it doesn't explicitly state when not to use it, the exclusion clarifies its limited scope.

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