finance-reconcile-mcp

Add Category Rule

setup_add_category_rule

Idempotent

Add or update a local category suggestion rule to automatically categorize transactions matching a pattern, without modifying external ledgers.

Instructions

Add or update a local category suggestion rule. 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": {
      "match": "<match>",
      "category": "<category>"
    },
    "name": "setup_add_category_rule"
  }
}

Input Schema

Name	Required	Description	Default
`match`	Yes
`category`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jul 29, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already indicate idempotent and non-destructive behavior. The description adds valuable context by clarifying it only modifies local config and never touches Firefly III or SimpleFIN, which goes beyond 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?

Description is two sentences with no unnecessary words, effectively conveying purpose and safety scope.

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?

Lacks parameter semantics and does not discuss return values or how the rule interacts with other tools (e.g., listing rules). For a simple tool, this is adequate but with gaps.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain what 'match' and 'category' mean. The agent must infer semantics from parameter names and constraints, which is insufficient.

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 the action ('Add or update') and the resource ('local category suggestion rule'), and distinguishes it from tools that interact with external systems by clarifying it only writes local config.

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?

Description implies usage (local config only) but does not explicitly state when to use this tool versus alternatives like setup_remove_category_rule or when not to use it.

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