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)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

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)
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions 'AI-first' and 'TSC-compressed by default', which adds some behavioral context (e.g., compression behavior), but lacks details on permissions, rate limits, side effects, or output format, which are critical for a tool analyzing events.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, with two sentences that efficiently convey the tool's purpose and a key behavioral trait. However, the second sentence could be more integrated with the first for better flow, slightly reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (analyzing events for causal chains), the description is reasonably complete with purpose and a behavioral hint. Since an output schema exists, it need not explain return values, but it lacks context on when to use versus siblings and detailed behavioral traits, leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents the parameters. The description adds no additional meaning about parameters beyond implying TSC compression is default, which is already covered in the schema for the 'tsc' parameter. Baseline 3 is appropriate as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with specific verbs ('analyze', 'return') and resources ('CUDA + host events'), and distinguishes it from siblings by mentioning 'causal chains with severity, root cause, and recommendations'. It also includes a unique 'AI-first' characteristic with TSC compression.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus its siblings (e.g., get_check, get_stacks). It mentions 'AI-first' and 'TSC-compressed by default', but this does not help an agent choose between alternative tools for analyzing events or data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

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