Skip to main content
Glama

crash_stack

Inspect a specific thread's stack frames from a crash dump after thread selection, returning symbols or module+RVA with paginated results and unwind failure reasons.

Instructions

Return stack frames for a thread.

Use after crash_threads to inspect a specific thread. Shows symbols when available, otherwise module+RVA. Paginated by limit/offset. Reports the reason if unwinding is unavailable.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "crash_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
thread_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a fair job: it discloses symbol-vs-module+RVA rendering, that results are paginated, and that unwinding failures are reported with a reason rather than silently returning nothing. It omits any explicit statement of side effects or permission requirements, though 'Return' strongly implies a read-only operation.

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

Conciseness5/5

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

Five short lines, zero filler, with the primary action and the prerequisite ordering front-loaded before rendering and pagination details. Every sentence supplies distinct information.

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?

An output schema exists, so return-value explanation is not strictly required, yet the description still adds useful rendering and failure-mode context. The remaining gap is parameter guidance (thread_id source/format, limit ranges) for a tool with no annotation coverage.

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 0%, so the description must compensate; it explains that limit/offset drive pagination, which adds meaning beyond the bare integer titles. However, thread_id — the only required parameter — is only implicitly covered via 'inspect a specific thread', and no defaults, bounds, or ID format are given.

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?

States a specific verb and resource ('Return stack frames for a thread') and positions itself relative to the sibling crash_threads ('Use after crash_threads'). An agent can tell exactly what it produces without opening the schema.

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

Usage Guidelines4/5

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

Explicitly gives the triggering context: call this after crash_threads when a specific thread needs inspection. It stops short of naming conditions where this tool is the wrong choice (e.g., comparing crashes, which crash_compare presumably covers), so it is clear context but not full when/when-not routing.

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