Skip to main content
Glama

convert_fintech

Convert OFX/QFX, QIF, or MT940 financial files to JSON or CSV by specifying input and output paths, with automatic format detection.

Instructions

Convert financial data: OFX/QFX (banking)→JSON/CSV, QIF (Quicken)→JSON/CSV, MT940 (SWIFT)→JSON/CSV

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": {
      "inputPath": "<inputPath>",
      "outputPath": "<outputPath>"
    },
    "name": "convert_fintech"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputPathYesAbsolute path to input financial data file
outputPathYesAbsolute path for output file (include extension)
inputFormatNoInput format (auto-detected if not provided)
outputFormatNoOutput format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never states whether an existing output file is overwritten, whether directories are created, what permissions are needed, or what happens on an unsupported/corrupt file – all material for a tool that writes to a caller-specified path.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence that front-loads the purpose and then lists the supported conversions with no filler. The arrow notation is terse but readable and every clause carries format information.

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?

With no output schema and no annotations, the description should say what the tool returns (e.g., the written file path or a status) and how overwrite/error cases behave. It covers the input-side format matrix well but leaves the output-side and failure semantics unaddressed.

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%, so the parameters are already documented, including the enums and the note that inputFormat is auto-detected when omitted. The description only restates the valid format combinations, adding no extra meaning such as extension conventions or how auto-detection interacts with a mismatched extension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (Convert) and resource (financial data) and enumerates the exact format pairs supported: OFX/QFX, QIF, and MT940 into JSON/CSV. That makes the domain unambiguous, though it never contrasts itself with the similarly named convert_spreadsheet or batch_convert siblings.

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?

Usage is only implied by the format list: an agent can infer it should be used for a single financial file in one of the three named input formats. There is no explicit statement about when to prefer batch_convert for multiple files, and no prerequisites such as readable input path or existing output directory.

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