FreeDailyPro Tools

business_bank_statement_to_csv

Read-onlyIdempotent

Bank statement to CSV

Input Schema

Name	Required	Description
`text`	No	The statement as pasted text. Send this, or a PDF in fileBase64 (or as the multipart field file).
`year`	No
`dateOrder`	No
`flipSigns`	No
`categorize`	No	true adds a category to every row from a short list of generic keywords (not a merchant database). Default false.
`fileBase64`	No	A text-based PDF statement, base64 encoded, up to 20 MB and 100 pages. Scanned or photographed PDFs are refused with a 422: there is no OCR.
`includeText`	No	true adds the lines read from the PDF to the response as extractedText, to see what the parser saw.
`numberFormat`	No
`categoryRules`	No	Your own rules: a row whose description contains match (any case) gets that category; the first matching rule wins, before the built-in keywords.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedNov 1, 2026

addedInput schema / properties / categorize

Added value: +{
+  "description": "true adds a category to every row from a short list of generic keywords (not a merchant database). Default false.",
+  "type": "boolean"
+}

addedInput schema / properties / categoryRules

Added value: +{
+  "description": "Your own rules: a row whose description contains match (any case) gets that category; the first matching rule wins, before the built-in keywords.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "category": {
+        "maxLength": 60,
+        "minLength": 1,
+        "type": "string"
+      },
+      "match": {
+        "maxLength": 100,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "match",
+      "category"
+    ],
+    "type": "object"
+  },
+  "maxItems": 200,
+  "type": "array"
+}

addedInput schema / properties / fileBase64

Added value: +{
+  "description": "A text-based PDF statement, base64 encoded, up to 20 MB and 100 pages. Scanned or photographed PDFs are refused with a 422: there is no OCR.",
+  "maxLength": 28000000,
+  "minLength": 8,
+  "type": "string"
+}

addedInput schema / properties / includeText

Added value: +{
+  "description": "true adds the lines read from the PDF to the response as extractedText, to see what the parser saw.",
+  "type": "boolean"
+}

addedInput schema / properties / text / description

Added value: +"The statement as pasted text. Send this, or a PDF in fileBase64 (or as the multipart field file)."

removedInput schema / required
```
Removed value: -[
-  "text"
-]
```

First observedOct 23, 2026

TDQS

D1.6/5.0

Behavior2/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. However, the description adds no behavioral context such as PDF limitations, OCR refusal behavior, or what the conversion returns.

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

Conciseness2/5

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

The four-word description is short but severely under-specified rather than concise. It is front-loaded with a restatement of the name and offers no actionable detail.

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

Completeness1/5

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

Given a 9-parameter conversion tool with no output schema and incomplete schema descriptions, the description is completely inadequate. It does not explain input modes, PDF restrictions, CSV output shape, or categorization behavior.

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?

With 9 parameters and only 56% schema description coverage, the description must compensate for undocumented parameters. It provides no parameter semantics at all, leaving options like year, dateOrder, flipSigns, and numberFormat unexplained.

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

Purpose2/5

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

The description merely restates the tool name and title as 'Bank statement to CSV'. It does not specify what conversion entails, what formats are accepted, or how this differs from the many sibling business document tools.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool, what inputs are appropriate, or what alternatives exist among the sibling tools.

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

All FreeDailyPro Tools tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?