ibanforge-mcp provides 11 well-named, domain-specific tools with clear descriptions and detailed input schemas. Tool names follow verb_noun conventions (validate_iban, lookup_bic, check_compliance) and are specific to their domain. Descriptions are substantive and include pricing information, aiding agent decision-making. All tools have explicit JSON Schema input definitions with type declarations and parameter descriptions. However, output schemas are not documented in the visible source, the mcp.json file defines inputs only. No tool annotations (readOnlyHint/destructiveHint/idempotentHint) are present, and error handling guidance is absent from the tool definitions. The server's main limitation is STDIO-only transport, which caps protocolReadiness but does not directly impact definition quality.

• Add output schemas to every tool definition. Specify response object structure, field types, and sample values. Example for validate_iban: '{"valid": boolean, "iban": string, "bank_name": string, "bic": string, "sepa_reachable": boolean, "risk_score": number (0-100), "swiss_bc_nummer": string|null}'
• Add tool annotations: mark validate_iban, batch_validate_iban, lookup_bic, lookup_ch_clearing, validate_payment_reference, check_postal_address, check_swiss_qr_bill as readOnlyHint=true; mark send_feedback, request_api_key as destructiveHint=true (they have side effects).
• Document mutual exclusion for check_compliance: add to required array one of [iban, bic] and clarify in description: 'Provide either iban OR bic, not both. If unsure of the BIC, use the IBAN and the tool will resolve it.'
• Add error recovery hints: 'If validation fails, check that spaces and formatting match ISO 13616. For multi-IBAN checks, call batch_validate_iban to identify which IBANs are invalid.'
• For request_api_key.device_code parameter, replace 'Leave empty' with a clear type and default: type='string|null', description='The device code from request_api_key(). Omit to reuse the last request from this session.' Make the default explicit.
• Expand check_postal_address.address schema: define the object properties with types, e.g., {type: 'object', properties: {strt_nm: {type: 'string'}, bldg_nb: {type: 'string'}, pst_cd: {type: 'string'}, ...}, required: ['pst_cd', 'twn_nm', 'ctry']}
• Add pricing context to descriptions where relevant. Example: 'This is a batch operation; use this instead of 10 single calls to reduce cost 4x.' Helps agents make efficient choices.