Skip to main content
Glama
stornoro

Storno CLI

by stornoro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

borderou_upload

Uploads a bank statement or borderou file to parse transactions and match them against existing invoices.

Instructions

Upload a bank statement or borderou file (CSV, XLSX, XLS, or the original bank PDF) for transaction import and reconciliation. PDF statements are recognised automatically for Banca Transilvania, BRD, ING, CEC, Raiffeisen, UniCredit, BCR, Revolut, Garanti, Libra, Patria, Intesa Sanpaolo, Citi, Vista, Wise, myPOS, Viva, Nexent and Trezoreria Statului (pick the matching provider or generic_bank). Parses the file, creates transactions, and runs automatic matching against existing invoices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyNoCurrency code (default: RON)
filePathYesAbsolute path to the file to upload (CSV, XLSX, XLS, or PDF)
providerYesBank or provider name (from borderou_providers)
companyIdNoCompany UUID override (uses active company if not set)
sourceTypeYesType of upload: "borderou" for payment lists, "bank_statement" for bank exports
bankAccountIdNoBank account UUID (for bank_statement type)
bordereauNumberNoBorderou reference number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.37
    • changedInput schema / properties / filePath / description
      Previous value: -"Absolute path to the file to upload (CSV, XLSX, or XLS)"New value: +"Absolute path to the file to upload (CSV, XLSX, XLS, or PDF)"
  2. First observedv1.0.17

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must convey behavior. It states that the tool parses the file, creates transactions, and runs automatic matching against existing invoices, which are key side effects. However, it does not detail idempotency, error handling, or whether matching modifies invoices, leaving some uncertainty.

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?

The description is well-structured and concise, with a clear first sentence summarizing the core function, followed by relevant details about file formats and bank recognition. It avoids redundancy and is easy to scan.

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?

Given the tool's complexity (7 parameters, no output schema), the description covers the main use case, supported formats, and the process. It does not explicitly explain every parameter interaction (e.g., bankAccountId usage), but the schema descriptions fill the gaps, making it reasonably complete.

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?

The schema has 100% coverage with descriptions for all 7 parameters. The description adds contextual value (e.g., file types, provider selection, source type meanings) but does not significantly surpass the schema's own explanations. Thus it meets the baseline for high schema coverage.

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?

The description clearly states the tool's purpose: uploading a bank statement or borderou file for transaction import and reconciliation. It specifies the file formats and the key actions (parses, creates transactions, runs matching). This is specific and distinguishes it from other borderou-related tools.

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?

The description provides practical usage context, such as supported file types and automatic PDF recognition for a list of banks, and instructs to pick the matching provider or generic_bank. While it does not explicitly name alternative tools or when not to use it, the context is sufficient for a typical user.

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