Skip to main content
Glama

get_causal_chains

Analyze CUDA and host events to identify causal chains explaining GPU latency, providing severity, root cause, and recommendations for debugging.

Instructions

Analyze CUDA + host events and return causal chains with severity, root cause, and recommendations. AI-first: TSC-compressed by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNotime range, e.g. 1m, 5m. Default: all data (0 = no time filter)
pidNofilter by single process ID. 0 = all. Deprecated: use pids.
pidsNofilter by process ID(s). Takes precedence over pid.
tscNotelegraphic compression (default: true)

Implementation Reference

  • The `get_causal_chains` tool is called via the `MCPClient.call` method in the `MCPClient` class. It is registered as a tool method for convenience within the investigation scripts.
    def get_causal_chains(self, since: str = "10m") -> dict:
        """Get causal chains (120s timeout — replay is expensive on large DBs)."""
        return self.call("get_causal_chains", {"since": since, "tsc": False}, timeout=120)

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ingero-io/ingero'

If you have feedback or need assistance with the MCP directory API, please join our Discord server