Skip to main content
Glama

WritersLogic agent-infra

test-exit-interpret

Interpret a test run: pass, no-tests, skipped, flaky, infra-failure from runner, exit code and counts — Reads a finished test run (runner, exit code, optional version, flags, caller-parsed counts, optional go test output, optional per-attempt exit codes) and says whether tests actually passed, ran nothing, were all skipped, passed only on retry, or never ran properly (timeout, signal, internal error). Encodes only exit-code semantics the runners document: pytest 0-5, node:test, mocha (failure count

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "runner": "<runner>"
    },
    "name": "test-exit-interpret"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNo
countsNoCounts parsed by the caller from the runner's own report.
outputNogo test output (only ok, FAIL, --- FAIL and panic: lines are read).
runnerYes
signalNoTerminating signal name, e.g. SIGKILL.
versionNoRunner version, e.g. 10.4.0. Needed only for version-gated flags.
exitCodeNoProcess exit status. Omit when the process was killed by a signal or timed out.
timedOutNoTrue when the harness gave up waiting.
attemptExitCodesNoExit codes of repeated runs of the same tests, to detect flakiness. Interpreted with the same runner rules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources