Skip to main content
Glama

crash_summary

Summarizes a loaded crash dump by reporting crash type, faulting address and thread, architecture, modules, and symbol resolution status so you can assess why it crashed.

Instructions

Return a short summary of the loaded dump.

Use to get crash type, faulting address, faulting thread, arch, module and symbol resolution status. Returns unknown for missing fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crash_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It usefully discloses that missing fields come back as "unknown" and that it operates on an already-loaded dump, but it never states what happens when no dump is loaded (error vs empty result) or whether the call is side-effect free.

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?

Two short sentences with the purpose front-loaded and the returned fields listed immediately after. No filler, no repetition of the name or title.

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?

For a zero-parameter read tool with an output schema covering the return shape, the description is nearly sufficient. The one gap is failure behavior when no dump is loaded, which matters for an agent sequencing calls after crash_load.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly spends no space on parameter explanation.

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

Purpose4/5

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

The description gives a specific verb and resource ("Return a short summary of the loaded dump") and then enumerates exactly what the summary contains: crash type, faulting address, faulting thread, arch, module, and symbol resolution status. That distinguishes it reasonably well from siblings like crash_stack or crash_threads, though it doesn't name them explicitly.

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

Usage Guidelines3/5

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

"Use to get crash type, faulting address..." implies the scenario but doesn't state prerequisites or exclusions explicitly. The phrase "the loaded dump" hints that crash_load must run first, but no alternative is named and no when-not guidance is given.

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