Check whether a release can ship

release.readinessChanges dataCreates, updates or deletes something in your workspace.

What it does

The ship gate for a release, sprint or milestone, from the test runs linked to it (testrun.create with releaseId). Each test case counts once, by its latest executed result across those runs. It is ready when at least one run is linked, no high case (priority P0 / P1 / High, or severity blocker / critical / high) failed or is still not executed, and no high-severity defect of the release (defect.create) is still open. Returns {ready, checks: [{key, label, ok, detail}], totals: {runs, cases, passed, failed, notExecuted, high}, blockers: [{testCaseId, caseId, title, priority, severity, status, testRunId}], otherFailures (failing, not high), runs, features: the features and stories linked to the release, defects: its open defects with blocking}. Deterministic. Read-only.

Ask your agent

You don’t call release.readiness yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:

  • “Can we ship v2.4?”
  • “What is blocking the June release?”
  • “Show the test status of Sprint 24”

Inputs

NameTypeDescription
releaseId
required
stringId of the release (the id from release.list).

The MCP call

What the agent’s MCP client sends (placeholders in angle brackets):

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "release.readiness",
    "arguments": {
      "releaseId": "<releaseId>"
    }
  }
}

Connect your agent

npx -y @testmaze/mcp init tmt_xxx
claude mcp add tm --scope project -- npx -y @testmaze/mcp

Create the token in your Test Maze workspace under Settings → MCP. Setup for Cursor, Cline, Gemini CLI and Codex CLI is shown there too.