What problem does it solve?
MCPJam eval results arrive as opaque wire enums like userValue, argumentMismatch, or evaluatorErrorRateAboveMaximum, and their meanings cannot be derived from the spellings. This Skill provides the authoritative definitions so you can correctly interpret a decisionSummary, a stage chain, or stage analytics without misreading counts, verdicts, or failure locations.
Core Features & Use Cases
- Complete vocabulary reference: Defines the six stages, five stage states, twenty-nine stage reasons, seven failure categories, four verdicts, and stage-analytics exclusion classes, verbatim from the SDK contract files.
- Population rules: Explains measurement units, zero-denominator handling, why
notEstablished is not a failure, and why stage tallies must never be summed across stages or runs.
- Comparability checks: Lists the parity blockers and partition keys that determine whether two funnels may legitimately be compared.
- Use Case: When an eval run returns
inconclusive with evaluatorErrorRateAboveMaximum, use this Skill to learn the validity phase ran and withheld a verdict because the evaluator failed too often — a decision about measurement quality, not a server defect.
Quick Start
Explain what the wire value argumentMismatch means in my MCPJam eval decision summary and whether this run's stage analytics can be compared with last week's run.
