Skip to main content
Glama

Stack-Trace Root-Cause Frame Isolator & Drain Log Deduplicator

isolate_stacktrace_root_cause
Read-onlyIdempotent

Parses noisy CI logs and multi-language stack traces to isolate the innermost failing user-code frame and cluster repetitive errors for triage debugging.

Instructions

Parses noisy CI/terminal logs and multi-language stack traces (Node/TS, Python, Rust, Go), strips node_modules/stdlib frames to isolate the innermost failing user-code frame, and clusters repetitive logs into Drain templates. Use when triage-debugging test failures, crash dumps, or repetitive server error logs; for compressing general source code files or prose transcripts, use prune_context_skeleton instead. Read-only edge call (32 KB, 60 RPM): accepts 'raw_log' ('runtime_hint' defaults to 'auto_detect'), supports '?demo=true' or L402 (15 sats), and returns HTTP 400 if invalid.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "raw_log": "<raw_log>"
    },
    "name": "isolate_stacktrace_root_cause"
  }
}

Input Schema

NameRequiredDescriptionDefault
raw_logYesRaw terminal output, CI failure log, or exception traceback to analyze.
runtime_hintNoRuntime stack format hint; defaults to 'auto_detect' when omitted.

Output Schema

NameRequiredDescriptionDefault
error_headlineYesExtracted primary exception class and error message.
root_cause_frameYesInnermost user-code stack frame (function_name, file, line, column).
root_cause_fingerprintYesDeterministic hash of the error class and root user frame.
deduplicated_log_templatesYesDrain-clustered log patterns with occurrence counts.
stripped_library_frames_countYesNumber of node_modules, stdlib, or internal frames filtered out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.3

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely useful operational context: 32 KB payload cap, 60 RPM rate limit, demo-mode or L402 payment of 15 sats, and HTTP 400 on invalid input. However, it is silent on the shape of the hybrid return (two distinct outputs from one call) and on truncation behavior when a log exceeds the 32 KB ceiling, which is the main behavioral risk for this tool.

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?

Front-loaded with the core action, then usage, then operational constraints — no filler sentences. It is dense to the point of being run-on in the final clause, packing call syntax, payment, and error code into one sentence, but every element carries information.

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

Completeness5/5

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

For a 2-parameter, fully-documented tool with an output schema, the description covers everything an agent needs before calling: purpose, alternative tool, limits, payment path, and failure mode. Return-value detail is correctly left to the output schema.

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 coverage is 100% and the enum is documented in-schema, so the description's mention of 'raw_log' and the 'runtime_hint' auto_detect default largely restates structured data. Baseline 3 is appropriate; it does not explain what happens on a mismatched runtime_hint versus auto_detect detection failure.

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?

Specific verbs and resource: parses CI/terminal logs and multi-language stack traces, strips node_modules/stdlib frames to isolate the innermost failing user-code frame, and clusters repetitive logs into Drain templates. The supported runtimes (Node/TS, Python, Rust, Go) and the dual output (isolated frame + dedup templates) make it unambiguous, and it names the sibling it is not (prune_context_skeleton).

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

Usage Guidelines5/5

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

Explicit positive triggers ('triage-debugging test failures, crash dumps, or repetitive server error logs') and an explicit exclusion routing the agent to prune_context_skeleton for general source files or prose transcripts. Nothing about tool selection is left to inference.

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

Deploy Server

Other Tools