Get one test case
testcase.getReadsOnly looks things up; never changes your workspace.What it does
Reads one test case in full: title, description, pre-condition, steps (in order), expected result, post-condition, priority, status, acceptance-criterion label, waiver details (isWaived, waivedReason, waivedBy, waivedAt), severity, automationStatus, the stored Playwright script if any (playwrightSnippet), the last recorded verdict (lastVerdict, lastVerdictAt) and its tags. Use it before case.update so you can resend the full step list, or to show a user what a test actually checks. Takes the internal id from case.list, not the human caseId. Read-only; a case from another workspace is refused.
Ask your agent
You don’t call testcase.get yourself. Say something like this to Claude Code, Cursor or another MCP-connected agent:
- “Show me the steps of the checkout test”
- “What exactly does GenTC-0004 check?”
- “Open the password reset test case”
Inputs
| Name | Type | Description |
|---|---|---|
caseIdrequired | string | Internal test case id: the id field from case.list (e.g. "AAtc-kzqd-mwpe-rtya-hbnc-xufo-lgsi"). Despite the parameter name, this is NOT the human caseId like "GenTC-0001"; passing that returns "not found". |
The MCP call
What the agent’s MCP client sends (placeholders in angle brackets):
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "testcase.get",
"arguments": {
"caseId": "<caseId>"
}
}
}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.
More test cases tools
- List test cases
case.list - Create a test case
case.create - Update a test case
case.update - Create several test cases at once
case.create_batch - Waive an acceptance criterion
case.waive_ac - Delete a test case
case.delete - Delete several test cases
case.delete_batch - Remove a waiver
case.unwaive_ac