Skip to main content
Glama

BRAINIAC Bank Account Identifiers & Payment Files

Validate a SEPA Creditor Identifier

bank-payments_sepa-creditor-id-validate
Read-onlyIdempotent

Parse a SEPA Direct Debit Creditor Identifier and recompute ISO 7064 Mod 97-10 check digits (business code excluded). Price $0.01 USDC. POST /api/v1/bank-payments/sepa-creditor-id-validate. An unpaid call returns the x402 payment terms and does not run.

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": {
      "creditorId": "<creditorId>"
    },
    "name": "bank-payments_sepa-creditor-id-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
creditorIdYescreditorId, string, length 8 to 40. Required.

Output Schema

NameRequiredDescriptionDefault
validNovalid. Boolean.
countryNocountry. String.
sourcesNosources. Array.
creditorIdNocreditorId. String.
checkDigitsNocheckDigits. String.
limitationsNolimitations. Array.
businessCodeNobusinessCode. String.
nationalIdentifierNonationalIdentifier. String.
expectedCheckDigitsNoexpectedCheckDigits. String.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior: the cost ($0.01 USDC), the fact that this is an x402-paid endpoint, and that an unpaid call does not execute but returns payment terms. It does not describe the verdict/response semantics, but an output schema exists to carry that.

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?

Four tight sentences, with the core purpose front-loaded before the payment and endpoint details; nothing is padding. Telegram style ('Price $0.01 USDC.', bare POST path) is efficient for an agent, though the endpoint restates information largely inferable from the tool name.

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 single-parameter validator with an output schema, annotations and a documented payment gate, an agent has what it needs to call it correctly. Only a hint about the expected identifier format and what an invalid result looks like is missing, and the output schema plausibly covers the latter.

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?

Only one parameter, and schema description coverage is 100%, so the schema already documents creditorId including its 8-40 length bound. The description adds conceptual detail relevant to the value (business code is excluded from the checksum) but no format/structure guidance such as country prefix plus check digits, so it does not exceed the baseline.

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 recompute') plus the exact resource ('SEPA Direct Debit Creditor Identifier') and even the algorithm (ISO 7064 Mod 97-10). That level of specificity clearly separates it from siblings like uetr-validate, iban-from-bban, nacha-file-validate and uk-modulus-check.

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?

The intended use is implied by the resource named, and the note about unpaid calls returning x402 payment terms tells the agent what happens on a payment failure. However, there is no explicit when-to-use/when-not guidance and no named alternative for validating other identifier types, so the agent must infer routing from the resource name alone.

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