Skip to main content
Glama

crash_disassemble

Disassembles memory around a crash address in a dump to inspect nearby instructions. Specify how many instructions to show before and after; returns an error if memory is unavailable.

Instructions

Disassemble memory around an address in the dump.

Use to inspect instructions near the crash address. before/after are instruction counts (capped). Returns an error if memory 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": {
      "address": "<address>"
    },
    "name": "crash_disassemble"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNo
beforeNo
addressYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 disclose real behavior: before/after are instruction counts that are capped, and the tool returns an error when memory is unavailable. That error precondition and the capping behavior are the kind of detail an agent needs to plan around. It does not state whether the operation is read-only or how large the cap is.

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 action, then usage, then error behavior in three short sentences. Nearly every sentence earns its place; only the usage line is slightly redundant with the opening.

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 values need not be explained. For a three-parameter tool the description is close to adequate, but the missing address format and the undisclosed cap value leave a gap an agent will likely hit in practice.

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 does explain that before and after are instruction counts and that they are capped, which adds meaning over the bare integer schema. However, the required 'address' parameter gets no format guidance (hex string, module+offset, pointer), leaving the single mandatory argument ambiguous.

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?

States a specific verb and resource: 'Disassemble memory around an address in the dump.' An agent can distinguish this from crash_stack or crash_summary without opening the schema, though the description never explicitly contrasts with those siblings.

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 inspect instructions near the crash address' gives a use context, but it largely restates the purpose line. No when-not guidance, no prerequisites, and no mention of an alternative tool for related analysis.

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