Check a user story's Definition of Ready and Done

userstory.gatesChanges dataCreates, updates or deletes something in your workspace.

What it does

The Definition of Ready and Done of one user story. Ready: the as a / I want / so that statement, at least one acceptance case, story points, agent-written spec reviewed by a person, and every Ready checklist item ticked. Done: every acceptance case passes (latest executed result across all runs) or is waived, spec reviewed, and every Done checklist item ticked. Checklists hold the workspace items plus the story's own (source policy / ai / manual). enforced says whether the workspace requires them: Ready before spec.start_work and before the story moves to in-progress, Done before it moves to live. Returns {storyId, ready: {ok, checks: [{key, label, ok, detail}], checklist: [{text, source, checked, checkedBy, checkedAt}]}, done: {...}, enforced: {ready, done}}. Read-only.

Ask your agent

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

  • “Is the saved-card story ready to start?”
  • “What is left before this story is done?”

Inputs

NameTypeDescription
suiteId
required
stringId of the user story (the suiteId from userstory.create or feature.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": "userstory.gates",
    "arguments": {
      "suiteId": "<suiteId>"
    }
  }
}

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.