Skip to main content
Glama

FinOps Studio Zero-Auth Bank Validator & 2-Row Taste-Test MCP

preview_bai2_statement_2_tx

Free 2-transaction taste-test preview of Corporate BAI2 bank statement parsing (records 01..99) into signed 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": {
      "bai2Content": "<bai2Content>"
    },
    "name": "preview_bai2_statement_2_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
bai2ContentYesRaw multi-line BAI2 bank statement text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers real behavior: the call is free, output is capped to a 2-transaction preview, supported input spans BAI2 records 01..99, and the result is signed JSON & CSV. It does not disclose what happens with larger inputs, unsupported records, or error conditions, which keeps it from a 5.

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 dense sentence with the differentiating information (BAI2, preview cap, output formats) front-loaded. 'Taste-test' is mild flavor wording but does not obscure meaning.

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?

For a one-parameter, annotation-free preview tool with no output schema, the description covers purpose, scope limits, and output formats sufficiently to invoke it correctly. Only the return shape and failure behavior remain unstated.

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% for the single bai2Content parameter, so the schema already establishes that it is raw multi-line BAI2 text. The description adds no syntax, size-limit, or format detail beyond that, so the baseline of 3 applies.

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?

Uses a specific verb (preview/parse) plus resource (Corporate BAI2 bank statement) and names the output formats (signed JSON & CSV), so the agent can tell it apart from the SEPA, NACHA, DATEV, and EU e-invoice preview siblings by format alone. It stops short of an explicit 'not for other formats' statement, which keeps it from a 5.

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?

'Free 2-transaction taste-test preview' implies this is a trial/limited-scope call rather than a full production parse, which is useful implied guidance. However, there is no statement of when to prefer this over a full-parse alternative, no prerequisites, and no exclusions.

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.