trace_hotspots

[diagnostics]

Summarizes CPU sample hotspots from collected runtime.nettrace artifacts for a GliderTrace session.

Try it locally in the GliderTrace playground

Parameters

Name	Type	Required	Description
sessionId	string	Yes	Trace session id, for example trc_20260507_123044_ab12cd34.
text	string	No	Optional case-insensitive filter across frame, method, module, module path, and source path.
limit	number	No	Maximum number of hotspot summaries to return. Default: `20`
includeRuntimeFrames	boolean	No	Include runtime/framework frames instead of preferring user-code frames. Default: `false`

Examples

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

Summarize runtime hotspots

Arguments 
{
  "sessionId": "trc_20260507_123044_ab12cd34"
}

Full MCP request

Full MCP request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_hotspots",
    "arguments": {
      "sessionId": "trc_20260507_123044_ab12cd34"
    }
  }
}

Response Notes

Returns CPU hotspot frames, sample counts, modules, source hints, and artifact context.

From GliderTrace 1.0.0: this tool records analysis gaps and warnings in the stored session. modulePath identifies the module binary. sourcePath remains null when no source-document evidence exists. Do not treat a module path as a source file. Inspect coverage and warnings before interpreting an empty result; an analysis failure does not prove that no samples exist.

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.