No user-submitted related servers found.
Scored across 13 tools
Each tool targets a distinct resource and action: refund policy, reconciliation, break explanation, disputes, contracts, and import each have clearly separate tools with no functional overlap. Even the potentially confusable pairs (propose_contract_terms vs save_contract_terms, preview_import vs import_transactions) are explicitly staged with descriptions clarifying sequencing. Descriptions proactively prevent misselection (e.g. check_refund_policy 'Does NOT issue the refund').
Every tool follows a consistent verb_noun snake_case pattern: check_refund_policy, list_contract_versions, explain_reconciliation_break, draft_evidence_pack, save_mapping_profile, import_transactions. There are no camelCase or other convention deviations, and verbs are used consistently for the same class of action (list_*, save_*, propose_*).
13 tools fall squarely in the well-scoped range, and each maps to a real operational step (setup, ingest, reconcile, explain, dispute, contract). No redundant or filler tools are present; each earns its place in the payments-ops workflow.
Coverage is strong across ingestion (preview/save_mapping/import), reconciliation (reconcile + explain), disputes (list/triage/draft), and contract lifecycle (list/propose/save). Minor gaps: there is no refund issuance tool (check_refund_policy explicitly stops short), no dispute submission, and no contract update/delete, but these appear to be intentional human-in-the-loop handoffs that agents can route around.