Skip to main content
Glama
Sign In
finance-mcp-server

finance-mcp-server

by Marcusdt-UX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Import Rocket Money CSV

finance_import_csv
Idempotent

Import a Rocket Money CSV export into a local finance store with automatic deduplication by row hash, ensuring only new transactions are added.

Instructions

Import a Rocket Money transaction CSV export into the local store. Idempotent: re-importing the same or an updated export dedupes by a stable row hash, so only genuinely new transactions are added. Args: path (absolute path to the .csv). Returns counts (parsed/inserted/skipped), the date span, and any parsing warnings.

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": {
      "path": "<path>"
    },
    "name": "finance_import_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to the Rocket Money CSV export

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Adds value beyond annotations: explains idempotency with 'dedupes by a stable row hash' and details return values (counts, date span, warnings). No contradiction with 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?

Three concise sentences, front-loaded with purpose, no unnecessary words. Efficient and clear.

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

Completeness5/5

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

Despite no output schema, description fully covers return structure and idempotency behavior. Tool is simple (1 param), and description provides all needed context.

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?

Only one parameter, 'path', fully described in schema. Description merely restates the schema. Baseline 3 as per rule.

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 'Import a Rocket Money transaction CSV export into the local store', providing a specific verb and resource. Among siblings (finance_data_overview, etc.), none perform CSV import, so it is well-distinguished.

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 idempotency and the effect of re-importing, which guides usage. No explicit when-not-to-use or alternative tools, but given the sibling list, it is clear this is the only import tool.

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

Deploy Server

Other Tools