trace_get_session

[analysis]

Returns GliderTrace session metadata, compact summary, artifact references, and optional top findings.

Try it locally in the GliderTrace playground

Parameters

Examples

Replace sample paths and symbol keys with values from your workspace.

Inspect a trace session

{
  "sessionId": "trc_20260507_123044_ab12cd34"
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_get_session",
    "arguments": {
      "sessionId": "trc_20260507_123044_ab12cd34"
    }
  }
}

Response Notes

Returns compact session metadata, summary counts, artifacts, and top findings. It carries a coverage block. The block reports incomplete when some evidence was dropped or bounded at capture.

From GliderTrace 1.0.0: Test summaries preserve numeric strings or unknown, with count status, source, scope, and available report subtotals. Missing count provenance in an older session does not establish exact counts. Capture coverage does not establish count certainty or source identity.

GliderTrace 1.0.0 returns compact JSON for every tool. Result fields appear beside success; there is no response-format parameter. success describes the tool call. Check the process or session status and exitCode separately. Scalar results and fields that conflict with reserved names appear under result.

To migrate an envelope consumer, read response.sessionId instead of response.data.sessionId. Stored sessions and exported files keep their formats. --max-response-chars limits response text to 60,000 UTF-16 characters by default. Use 0 to disable it, or at least 1,000. This limit counts text characters, not transport bytes or tokens.

outputLimit.truncated marks omitted response detail. It does not change capture completeness. Use the returned next tool and arguments when available. Do not repeat a command or feedback submission to recover omitted output. For event pages, keep the filters and cursor while reducing limit.

For session details, set includeArtifacts and includeTopFindings to false to reduce output. Check error, actionable meta, warnings, and coverage before drawing conclusions. Internal diagnostics stay in local server logs.