finance-mcp-server

Overview Schema Source Related Servers Discussions Admin

Sync Bank (SimpleFIN)

finance_sync

Pull new transactions and refresh balances from a linked SimpleFIN bank account. Deduplicates by provider id to avoid double-counting.

Instructions

Pull new transactions and refresh balances from SimpleFIN. By default fetches from the day after the latest transaction already in the store (so it won't re-pull or double-count history from your CSV) — pass days_back to force a wider window (e.g. 365 for a full refresh). Transactions dedupe by provider id. Requires finance_link_bank first. Args: days_back (optional, 1-730). Returns { accounts, newTransactions, store_span }.

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

Input Schema

Name	Required	Description	Default
`days_back`	No	Override: fetch this many days back instead of since the last stored transaction

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Discloses side effect (refreshing balances), deduplication by provider id, and default non-re-pull behavior. Annotations do not provide such details, so description adds valuable transparency. 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?

Two sentences plus args/return notes, no fluff. Front-loaded with purpose, then default behavior, dedup, prerequisite, and structured args/return summary.

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

Completeness4/5

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

Covers purpose, default vs override, deduplication, prerequisite, and return fields (accounts, newTransactions, store_span) despite no output schema. Missing: behavior when no prior transactions exist, but overall sufficient for a simple tool.

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

Parameters4/5

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

Schema covers 100% of parameters with description. The tool description adds context: default behavior (since last stored transaction) and an example (365 for full refresh), which goes beyond the schema's 'Override' description.

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?

Clearly states the tool pulls new transactions and refreshes balances from SimpleFIN. Distinguishes from sibling tools like finance_import_csv (CSV import) and finance_balances (just balances) by specifying the source and action.

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?

Explains default incremental behavior (from day after latest transaction) and when to use days_back for full refresh. Mentions prerequisite finance_link_bank. Does not explicitly state when not to use, but the context is clear.

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

Deploy Server