trace_query_events

[analysis]

Queries normalized GliderTrace evidence events by session, kind, text, severity, and cursor.

Try it locally in the GliderTrace playground

Parameters

Name	Type	Required	Description
sessionId	string	Yes	Trace session id, for example trc_20260507_123044_ab12cd34.
kinds	json	No	Optional evidence kinds such as testFailure, exception, buildError, buildWarning, log, counter, process, artifact, or warning.
text	string	No	Optional case-insensitive text search across summary, message, test case, and stack frames.
minSeverity	string	No	Optional minimum severity: 'info', 'warning', 'error', or 'critical'.
limit	number	No	Maximum number of matching items to return. Default: `50`
cursor	string	No	Pagination cursor returned by a previous query.

Examples

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

Find exception events in a session

Arguments 
{
  "sessionId": "trc_20260507_123044_ab12cd34",
  "kinds": [
    "exception"
  ]
}

Full MCP request

Full MCP request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_query_events",
    "arguments": {
      "sessionId": "trc_20260507_123044_ab12cd34",
      "kinds": [
        "exception"
      ]
    }
  }
}

Response Notes

Returns matching normalized events, a pagination cursor, severity counts, and artifact context. It carries a coverage block. An incomplete block adds a warning. A zero-match page may still hide dropped events. Paging is a presentation limit, not incompleteness.

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.