Check where a PDLC session is in the loop

pdlc.statusReadsOnly looks things up; never changes your workspace.

What it does

Shows which step a PDLC session has reached. A PDLC session is an optional tracker of where you are in the product loop: plan → write tests → code → verify → ship. It is opened by project.initialize and moved forward by feature.implement, feature.verify and pdlc.verify when you pass them its sessionId. Returns state: INTAKE (just started), PLAN (feature planned), AUTHOR (writing tests), CODE (writing code), VERIFY (grading), REPAIR (fixing a broken test), SHIP (ready to release) or DONE; plus sessionId, spaceId and updatedAt. prdId, planId and currentStep are reserved and currently always null. Read-only: it never changes the state. Use it to resume after a break and decide which loop tool to call next.

Ask your agent

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

  • “Where did we get to with the password reset feature?”
  • “What step of the plan-test-code-ship loop am I on?”

Inputs

NameTypeDescription
sessionId
required
stringPDLC session id, e.g. "pdlc…": the sessionId returned by project.initialize, or an id from pdlc.list. Must belong to the connected workspace.

The MCP call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "pdlc.status",
    "arguments": {
      "sessionId": "<sessionId>"
    }
  }
}

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.