heap-seance
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAT_BIN | No | Path to ParseHeapDump.sh (macOS/Linux) or .bat (Windows). Required for deep mode forensics. | |
| JAVA_HOME | No | JDK 17+ installation path — $JAVA_HOME/bin is searched first for jcmd, jmap, jstat, jfr. Also used to launch MAT with the correct Java version. | |
| ASYNC_PROFILER_BIN | No | Path to async-profiler binary — tie-breaker evidence, deep mode works without it. | |
| HEAP_SEANCE_ARTIFACT_DIR | No | Where .jfr, .hprof, and reports are saved (default: system temp dir). |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| java_list_processesD | – |
| java_gc_snapshotD | – |
| java_class_histogramD | – |
| java_jfr_startD | – |
| java_jfr_summaryD | – |
| java_heap_dumpD | – |
| java_mat_suspectsD | – |
| java_async_alloc_profileD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Tools cover distinct diagnostic actions—process listing, heap dump, class histogram, MAT suspects, JFR start/summary, GC snapshot, allocation profile—so an agent can usually pick based on the futored operation. Minor proximity exists between heap_dump and class_histogram, but names plus conceptual roles keep them separate.
All names share the java_ prefix and snake_case, which helps. However, the verb placement is inconsistent: list_processes and jfr_start use a verb, while mat_suspects, class_histogram, and gc_snapshot are pure noun phrases without an obvious action word.
Eight tools is well within the ideal range for a focused Java diagnostics server. Each tool covers a distinct diagnostic technique (JFR, heap analysis, allocation profiling, GC snapshots), and none feel redundant or extraneous.
The server covers the core heap and JFR workflows: process discovery, heap dumps, class histograms, MAT suspect analysis, and JFR capture/summarization. The main gap is the lack of a JFR stop or thread dump tool, but agents can still achieve the primary diagnosis goals.