Skip to main content
Glama

iban_sepa_antifraud

Read-onlyIdempotent

[Deterministic banking validation. Pure calculation, read-only, side-effect free]. Performs ISO 13616 MOD-97 mathematical validation, SWIFT BIC identification, Peppol directory participant routing lookup, and geographic country coherence cross-check for Business Email Compromise (BEC) and wire fraud prevention. Usage: Use this tool to verify bank account format legitimacy and detect geographic discrepancies between supplier declared country and bank routing country before releasing SEPA payments. Returns: JSON object with { isValid: boolean, iban: string, country: string, bic: string, bankName: string, isDomesticMatch: boolean, fraudRiskScore: number, warnings: string[] }.

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": {
      "iban": "<iban>"
    },
    "name": "iban_sepa_antifraud"
  }
}

Input Schema

NameRequiredDescriptionDefault
ibanYesInternational Bank Account Number (IBAN) (e.g. IT02L1234512345000000012345)
domainNoSupplier website or email domain (e.g. supplier.it)
vatCountryNoExpected supplier VAT country code (e.g. IT) for discrepancy detection
expectedCompanyNameNoExpected beneficiary name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / iban / description
      Previous value: -"International Bank Account Number (IBAN)"New value: +"International Bank Account Number (IBAN) (e.g. IT02L1234512345000000012345)"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces determinism while adding the fraud-risk framing and a full enumeration of return fields (isDomesticMatch, fraudRiskScore, warnings) that would otherwise be unknown since no output schema exists. The one soft spot is internal: calling it 'pure calculation, side-effect free' sits awkwardly with the Peppol directory routing lookup, which implies an external dependency; auth and rate-limit behavior are unaddressed.

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?

Three labelled sections (what it does, usage, returns) with the core identity front-loaded and no filler sentences. The bracketed '[Deterministic... read-only, side-effect free]' prefix partly restates the annotations, which is the only wasted 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?

With four parameters, one required, no output schema, and a network-dependent lookup, the definition covers purpose, timing, and return shape well enough to call correctly. It stops short of documenting failure modes (invalid checksum, unknown BIC, no Peppol match) or what fraudRiskScore thresholds mean, which an agent interpreting the result would need.

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 iban, domain, vatCountry, and expectedCompanyName are already documented individually. The description adds only indirect meaning, tying 'supplier declared country vs bank routing country' to the discrepancy feature and implying why domain/name are supplied, but it never explains how domain or expectedCompanyName actually feed the fraud score.

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 names a specific resource (IBAN/SEPA/BIC) and enumerates the exact operations: ISO 13616 MOD-97 validation, SWIFT BIC identification, Peppol participant lookup, and country coherence cross-check. An agent can immediately separate this from the sibling tools, which audit tax codes, e-invoice XML, and KYB/VAT respectively.

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?

It gives an explicit trigger condition: verify IBAN legitimacy and detect declared-country vs routing-country discrepancies before releasing SEPA payments. That is a clear usage context, but there is no when-not-to-use statement and no sibling is named as an alternative (e.g. for cases where the agent actually needs VAT/KYB verification rather than IBAN validation).

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