Skip to main content
Glama

parse_bai2_statement

Read-onlyIdempotent

Parse corporate BAI2 cash-management bank statements into structured JSON or CSV to support reconciliation, ledger import, and audit.

Instructions

Parse corporate BAI2 (.bai / .bai2) cash-management bank statements (records 01, 02, 03, 16, 88, 49, 98, 99) into structured JSON and CSV via Apify Cloud.

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": {
      "bai2_content": "<bai2_content>"
    },
    "name": "parse_bai2_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
bai2_contentYesRaw multi-line corporate BAI2 bank statement text (records 01 through 99).
include_inline_csvNoWhen true, include a flattened UTF-8 CSV ledger export in the output.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds value beyond them by naming the output formats (structured JSON and CSV) and disclosing that execution happens 'via Apify Cloud', which signals an external service call. It stops short of mentioning cost, latency, or credential requirements for that cloud call.

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?

A single front-loaded sentence with the action, input format, supported records, and output formats in that order. The record-type list is dense but genuinely informative rather than filler, and there is no redundant or hedging wording.

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?

With no output schema, the description usefully compensates by stating that output is structured JSON plus optional CSV. For a two-parameter, annotation-rich parser this covers what an agent needs to invoke it correctly. It does not describe failure behavior for malformed or partially valid statements, which is the main remaining gap.

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 description coverage is 100% and only two parameters exist, so the schema already explains bai2_content and include_inline_csv thoroughly. The description's mention of CSV output loosely corresponds to the include_inline_csv toggle but adds no syntax, format, or edge-case detail beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (parse) and resource (corporate BAI2 cash-management bank statements), plus the file extensions (.bai/.bai2) and supported record types (01, 02, 03, 16, 88, 49, 98, 99). This makes it immediately distinguishable from format-specific siblings such as parse_pain002_status_xml and from the generate_* family, which produce files rather than parse them.

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 implied rather than stated: the extension and record-type enumeration tell an agent this is for BAI2 input, but there is no explicit when-to-use/when-not guidance and no alternative tool is named. An agent can infer the trigger condition, but must decide unaided what to do with a non-BAI2 file or how this relates to audit_bank_file_format.

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