Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
crash_loadA

Load a crash dump (ELF core or Windows minidump) into the session.

Use first, before any other crash_* tool. Detects format, architecture, threads, modules and exception info. Does not execute the dump. Missing binaries/symbols are reported, not guessed.

crash_summaryA

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.

crash_threadsA

List threads in the loaded dump.

Use to find the faulting thread or inspect thread states. Supports limit/offset pagination.

crash_stackA

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.

crash_disassembleA

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.

crash_compareB

Compare two crash dumps.

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

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool maps to a distinct action in a clear pipeline: load the dump, summarize it, enumerate threads, unwind a stack, disassemble at an address, and compare two dumps. Descriptions explicitly sequence the tools (load first, stack after threads), so there is no realistic misselection between them.

Naming Consistency5/5

All six tools use the same crash_ prefix followed by a short lowercase noun/verb token (load, summary, threads, stack, disassemble, compare). The pattern is uniform and predictable, making the set easy to scan.

Tool Count5/5

Six tools is a tight, well-scoped surface for crash dump triage; every tool has a distinct job and none appear redundant. Nothing feels padded or arbitrarily split.

Completeness4/5

The core workflow (load → summary → threads → stack → disassemble → compare) is fully covered, including pagination and graceful error reporting. However, there is no register inspection, module listing, or memory/string search tool, which are common needs in crash analysis and would force workarounds.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues