clickmax-failure-diagnosis

As tools abaixo aparecem com os nomes que o MCP da Clickmax registra. Se o seu cliente de IA prefixar nomes de tool (mcp__<servidor>__, mcp_<servidor>_, ou outro), use o nome já prefixado que aparecer na sua lista de tools.

When this applies

Use this skill when the seller wants to understand WHY transactions fail and what to do about it: failures grouped by reason, recoverable value per reason, and the recommended next action.

Not this skill:

• headline KPIs / paginated dashboard browsing / generic loss cohorts -> clickmax-payments-dashboard-analysis
• inspecting or refunding a specific transaction -> clickmax-transaction-operations
• accrued platform-fee debt -> transactions_debt (this is money the seller owes the platform, NOT a failed sale; never use it for failure diagnosis)

Key assumptions

• transactions_failure_breakdown already aggregates FAILED transactions into stable code buckets with count, recoverable value, and isPlatformFault, sorted by value.
• code is a stable category derived from the gateway's free-text reason; rawReasons holds the original strings that fell into each bucket.
• unknown means the gateway reason did not match a known pattern — lean on rawReasons to describe it.
• value mirrors the dashboard's failed-value semantics; render it as currency, do not re-scale it against other tools.
• count/value are per ATTEMPT: one buyer retrying N times counts N → say "tentativas", never "pessoas"; the deduplicated recoverable total is recovery_recoverable_revenue, not the sum of this breakdown.