Skip to main content
Glama

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

preview_sepa_xml_2_rows

Free 2-row taste-test preview of 2026 EPC structured-address ISO 20022 SEPA Credit Transfer (pain.001.001.09) & Direct Debit (pain.008.001.08) XML generation.

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": {
      "initiatingPartyName": "<initiatingPartyName>",
      "initiatingPartyIban": "<initiatingPartyIban>",
      "transactions": "<transactions>"
    },
    "name": "preview_sepa_xml_2_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
schemaNopain.001.001.09
transactionsYes
initiatingPartyBicNo
initiatingPartyIbanYes
initiatingPartyNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose genuinely useful behavior the schema cannot: the output is XML, the cap is two rows, and the call is free (implying cost/rate-limit context). It stops short of saying what happens if more transactions are supplied, whether input data is validated, or whether failures return partial XML.

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 front-loaded sentence with no filler; the preview scope and format are stated first. It is dense with standards jargon (EPC, ISO 20022, pain.001.001.09), but every clause carries information.

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

Completeness2/5

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

For a tool whose central input is an array of unstructured objects, with 0% schema coverage and no output schema, the description should sketch the transaction fields and the two-row truncation behavior. It leaves the agent unable to construct a valid transactions payload without guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters, and the description adds essentially nothing: initiatingPartyName, initiatingPartyIban and initiatingPartyBic are never explained or tied to the two schemas. Most critically, the transactions array is an untyped object with no item schema, and 'structured-address' is the only hint about its shape — far too thin for the core input.

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?

States a concrete verb (preview/generate) and resource (SEPA pain.001.001.09 credit transfer / pain.008.001.08 direct debit XML) with the ISO 20022 version pinned. That resource naming effectively separates it from the sibling preview tools for EU e-invoice, DATEV CSV, NACHA ACH and BAI2, though it never explicitly says so.

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-row taste-test preview' implies the intended context: sampling output before committing to real generation. But there is no explicit when-to-use, no when-not-to-use, and no pointer to a full-generation or validation tool (e.g. validate_global_bank_identifiers) for anything beyond a two-row sample.

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.