Skip to main content
Glama

BRAINIAC Bank Account Identifiers & Payment Files

CBPR+ postal address format check

bank-payments_postal-address-check
Read-onlyIdempotent

Classify an ISO 20022 PostalAddress as structured, hybrid or unstructured and check Swift CBPR+ town/country/AdrLine rules. Price $0.02 USDC. POST /api/v1/bank-payments/postal-address-check. 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": {
      "address": "<address>"
    },
    "name": "bank-payments_postal-address-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNorole, string, one of party, agent. Required.party
addressYesaddress, object. Required.
agentHasBicNoagentHasBic, boolean. Optional.
messageTypeNomessageType, string, length 1 to 32. Optional.

Output Schema

NameRequiredDescriptionDefault
exemptNoexempt. Boolean.
formatNoformat. String.
issuesNoissues. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
cbprCompliantNocbprCompliant. Boolean.
cbprRetirementDateNocbprRetirementDate. Null.

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, openWorld and non-destructive, so the description's added value is the x402 payment gate: cost ($0.02 USDC) and the fact that an unpaid call returns payment terms instead of executing. That is genuinely useful behavior an agent cannot infer from structured fields, though failure semantics for a malformed address are not described.

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 compact sentences, front-loaded with purpose before cost and transport details. The 'POST /api/v1/bank-payments/postal-address-check' line is largely redundant with the tool name but is a small fraction of the text.

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?

An output schema exists, so return values needn't be spelled out, and the nested address object's field rules are delegated to a 100%-covered schema. The main residual gap is what happens when an address fails the checks (error vs. a 'non-compliant' classification) and what 'hybrid' means concretely.

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%, so the baseline is 3. The description does add meaning by naming the town/country/AdrLine rules, which maps to TwnNm, Ctry and AdrLine, but the role, agentHasBic and messageType parameters are left entirely to the schema.

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 pair (classify, check) plus the exact resource (ISO 20022 PostalAddress under Swift CBPR+ rules) and enumerates the classification outputs (structured/hybrid/unstructured). An agent can distinguish this from siblings like iban-from-bban or uetr-validate purely on the resource being validated.

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?

Usage is implied by the CBPR+ / postal address framing, but the description never says when to call it (e.g. pre-validation before a pacs.008 build) or when a sibling such as camt053-parse is the better choice. No exclusions or preconditions are stated beyond the payment requirement.

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