Skip to main content
Glama

Binyan.im · בניינים

Import bank statement

import_bank_statement
Idempotent

Import a JSON or PDF bank statement (base64, up to 3 MB). Skips exact duplicates (listed in duplicatesSkipped), imports but flags look-alikes with a different description (possibleDuplicates), records the balance the statement reports instead of importing balance lines as transactions, and returns the last bank-synced balance and the unmatched transactions. Bank import tools are available only when a building has bank sync configured.

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": {
      "buildingId": "<buildingId>",
      "fileBase64": "<fileBase64>",
      "filename": "<filename>",
      "mimeType": "<mimeType>"
    },
    "name": "import_bank_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
mimeTypeYes
buildingIdYes
fileBase64Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the deduplication policy (exact duplicates skipped, look-alikes with differing descriptions imported but flagged via possibleDuplicates), how balance lines are handled (statement balance recorded rather than imported as transactions), and what is returned (duplicatesSkipped, possibleDuplicates, last bank-synced balance, unmatched transactions). This explains why idempotentHint=true actually holds, which the annotations alone cannot convey.

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 dense paragraph with the core action front-loaded, followed by duplicate handling, balance semantics, and the availability caveat in priority order. Every clause carries information the agent needs; nothing is padding.

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 does the heavy lifting by enumerating returned fields, and it covers the availability precondition and file limits. The only remaining gap is the meaning of buildingId and how scope interacts with the bank-sync configuration, which is minor for an otherwise thoroughly described mutation tool.

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 0% for four required parameters, so the description must compensate. It does add real value for fileBase64 (base64 encoding, 3 MB cap) and implicitly for mimeType (JSON or PDF), but it says nothing about buildingId or filename constraints, leaving half the parameters undocumented in both schema and 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?

States a specific verb (import) and resource (bank statement) plus accepted formats (JSON or PDF, base64, up to 3 MB), so an agent can immediately tell this is a file-ingest tool rather than a transaction-listing or reconciliation tool such as list_unmatched_transactions or reconcile_transaction.

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?

Provides a concrete precondition — 'Bank import tools are available only when a building has bank sync configured' — which tells the agent when the tool is callable at all. It stops short of naming alternatives or stating when not to use it (e.g. when a statement was already partially imported and should be reconciled instead).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources