Sign in
Eval runs

Get a run's decision summary

The canonical, versioned run decision contract: the verdict and where it came from, the counts with the population they count, the run's own verdict decision when it has one, and one page of per-trial diagnostics carrying the user-value chain, the first failed stage, the failure category, evidence scoped to that stage, and one next action.

ADDITIVE and composed: it is the same two reads a caller could make by hand (GET …/eval-runs/{runId} and GET …/iterations), assembled once here so every client shares one reading of a run instead of inventing its own. cursor and limit page the DIAGNOSTICS using the same cursors the iterations endpoint issues, and diagnostics.complete says honestly whether the page you got is the run's whole non-passing set.

get/projects/{projectId}/eval-runs/{runId}/decision-summary

Path parameters

projectIdstring required

ID of the hosted project that contains the server.

runIdstring required

Eval run ID, as returned by POST /eval-runs.

Query parameters

limitinteger

Iterations examined per page, 1–200. Defaults to 50.

cursorstring

Opaque cursor from a previous response's diagnostics.nextCursor. A page fetched with one is never reported as complete.

Response

The run's decision summary.

schemaVersion1 required
runIdstring required
runStatusstring required

The run's lifecycle status, verbatim. Not a verdict.

verdict'passed' | 'failed' | 'inconclusive' | 'notEstablished' required
verdictSource'policyV2' | 'legacy' | 'none' required

policyV2 — the run's own decision, carried on decision; verdict is its verdict. legacy — a percent-threshold run predating policy v2; there is no decision object and any counts are trials. none — no verdict; verdict is notEstablished and undecided says why.

decisionobject

The run's authoritative v2 verdict decision, copied verbatim after validation — the same shape as EvalRun.verdictSummary, published at https://mcpjam.com/schemas/eval-verdict-policy/v2.json. Present exactly when verdictSource is policyV2.

Changes

Changed in 1 of the 73 revisions of this API.1