Finish an exploration session

exploration.finishChanges dataCreates, updates or deletes something in your workspace.

What it does

Closes an exploration session so no more observations can be added. Call it when observe reports coverage.done, or when you decide to stop. Use status "completed" (default) when the walk is worth keeping and turning into test cases; use "abandoned" when you gave up (wrong URL, login wall, browser broke). Both keep the record. It builds a navigation tree (the visited pages arranged by URL path) and saves the URL and title checks of every visited page. Returns the summary: id, status, steps, pages, errors, verifiedShare (share of judged steps that were verified, 0–1), startedAt, endedAt. Calling it on an already closed session changes nothing and returns the summary. Only the user who started it can finish it. Next: exploration.to_cases to draft test cases, or exploration.get for the full record.

Ask your agent

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

  • “That's enough exploring, wrap it up”
  • “Stop the exploration, the login page is blocking us”

Inputs

NameTypeDescription
sessionId
required
stringThe sessionId returned by exploration.start.
status
optional
enum"completed" (default): the exploration ran its course. "abandoned": you stopped early and the record is not meant to be used.
Allowed: completedabandoned

The MCP call

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

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "exploration.finish",
    "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.