Skip to main content
Glama

crash_compare

Compare two crash dumps to check whether they share crash type, faulting address, module, and thread counts; missing symbols are reported as best-effort.

Instructions

Compare two crash dumps.

Use to check whether two crashes have the same type/address/module/thread counts. Best-effort; missing symbols are reported.

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": {
      "dump_path_a": "<dump_path_a>",
      "dump_path_b": "<dump_path_b>"
    },
    "name": "crash_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
dump_path_aYes
dump_path_bYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one meaningful trait: the comparison is "best-effort" and missing symbols are reported. It omits other important behavior such as whether the dumps must first be loaded via crash_load, permission requirements, or whether the operation is read-only and safe to repeat.

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?

Two short sentences, purpose stated first with the applicability note following, and no filler. The terseness is slightly under-specified rather than padded, which keeps it at 4.

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

Completeness3/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 needed, and the comparison dimensions are defined. However, for a two-argument tool with zero schema coverage and no annotations, the description should clarify dump-path prerequisites and best-effort failure modes more concretely.

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

Parameters2/5

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

Schema description coverage is 0% and both parameters are bare strings with only titles like "Dump Path A". The description adds nothing about whether these are filesystem paths or handles returned by crash_load, nor any format or constraint, so it fails to compensate for the coverage gap.

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?

Opens with a specific verb+resource ("Compare two crash dumps") and the next sentence names the exact dimensions compared (type/address/module/thread counts), so the agent knows what the result means. It stops short of naming how it differs from siblings like crash_summary or crash_stack, which is why it isn't a 5.

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?

"Use to check whether two crashes have the same type/address/module/thread counts" gives a concrete selection context for the tool. There is no explicit when-not guidance or mention of alternatives, so it lands at 4 rather than 5.

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