Skip to main content
Glama

elf_crash_backtrace_decode

Decode ESP32 Backtrace: 0x400... and ARM/RISC-V PC/LR/MEPC crash logs against an ELF symbol table (.symtab).

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": "elf_crash_backtrace_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoCrash log text containing Backtrace: or PC: hex addresses.
elfPathNoOptional local path to firmware.elf.
elfBase64NoOptional base64-encoded firmware.elf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it omits key behavior. With all three parameters optional, it never says what happens if neither elfPath nor elfBase64 is given (raw-address passthrough? error?), whether symbols are demangled, or how unresolved addresses are reported.

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?

A single dense sentence with the action and both supported log families front-loaded, and no filler. The telegraphic phrasing ("0x400...", "PC/LR/MEPC") is efficient for the audience, though slightly terse for anyone unfamiliar with those registers.

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?

The description covers input side adequately but says nothing about the primary deliverable — the decoded, symbol-annotated backtrace — and there is no output schema to fall back on. For a tool whose whole value is the resolution result, that leaves a meaningful gap.

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 each property already documents itself (crash log text, optional local ELF path, optional base64 ELF). The description adds only the fact that resolution targets .symtab, which is marginal beyond the schema; a baseline 3 applies.

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 ("Decode") plus the exact input formats it handles: ESP32 "Backtrace: 0x400..." logs and ARM/RISC-V PC/LR/MEPC dumps, resolved against an ELF .symtab. That is concrete enough to separate it from unrelated siblings like binary_triage or disassemble_wasm_or_hex, though the description never explicitly contrasts with them.

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

Usage Guidelines2/5

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

No when-to-use or when-not guidance is given; the agent must infer from the input examples (a crash log containing hex addresses) that this tool applies. There is no mention of prerequisites such as needing a matching firmware ELF, nor of what to do when no symbol table is available.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources