Scored across 21 tools
Most tools target clearly distinct resources or actions, and descriptions explicitly cross-reference alternatives such as validate_records vs validate_payment_scheme and parse_camt053 vs parse_pain002. Minor overlap remains between generate_message and generate_message_async (same operation with different execution context) and between get_required_fields and get_input_schema (subset vs full schema), so misselection is still possible but uncommon.
Every tool uses snake_case with a leading verb (list_*, get_*, validate_*, generate_*, parse_*, convert_*, inspect_*, sanitize_*), and domain-specific names like parse_camt053 and convert_mt101 still fit the verb-noun pattern. There is no camelCase or mixed convention.
21 tools is on the heavy side for a single server. While the ISO 20022 domain is broad, some tools are thin variants (generate_message_async) and several introspection tools could potentially be consolidated, placing this in the borderline 16-25 range.
The surface covers discovery, schema and required-field inspection, record and XML validation, scheme validation, generation from memory and CSV, migration, MT101 conversion, charset sanitisation, and parsing of camt.053 and pain.002 replies. Minor gaps remain: there is no parse_pain001 round-trip from XML back to records and no explicit listing of payment-scheme profiles, though agents can work around these.