Scored across 13 tools
Most tools have clearly distinct purposes, and the extensive USE WHEN/DO NOT USE guidance strongly separates them. A few pairs still share core behavior—check_compliance returns full validate_iban enrichment, and audit_creditor_file overlaps with batch_validate_iban on list-level validation—so an agent skimming names could pick the wrong one.
All tool names follow a consistent verb_noun snake_case pattern: validate_*, check_*, lookup_*, audit_*, send_*, request_*, poll_*. Even compound names like batch_validate_iban and check_swiss_qr_bill remain predictable and readable.
Thirteen tools is well within the ideal range and every tool earns its place: nine cover distinct payment-validation/lookup domain tasks, and the remaining four support async file auditing, API-key acquisition, and feedback. The count matches the server's broad but coherent scope.
The domain is covered end to end: single IBAN validation, batch validation, payment-reference validation, QR-bill checking, postal-address checking, BIC/IID lookup, compliance triage, and full creditor-file auditing. The async workflows are not dead ends—audit_creditor_file pairs with audit_status, and request_api_key pairs with poll_api_key—so agents can complete the full intended lifecycle.
