trace_hotspots

[diagnostics]

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

Why this tool exists

Raw runtime artifacts are usually too large and noisy for direct prompt use.

How it helps the agent

The model can ask for compact exception, counter, hotspot, or code-correlation summaries with stable session ids.

Try it locally in the GliderTrace playground

Parameters

NameTypeRequiredDescription
sessionIdstringYesTrace session id, for example trc_20260507_123044_ab12cd34.
textstringNoOptional case-insensitive filter across frame, method, module, and source path.
limitnumberNoMaximum number of hotspot summaries to return.
includeRuntimeFramesbooleanNoInclude runtime/framework frames instead of preferring user-code frames.

Examples

Summarize runtime hotspots

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.

↑/↓ NavigateEnter OpenSpace Expand