jvm-doctor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| 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 |
|---|---|
| thread_dumpA | 抓一次线程快照，返回归并后的视图与死锁检测结果。 |
| gc_statC | 堆各代使用率、GC 次数与累计停顿。 |
| heap_histogramB | 堆内对象占用 Top-N。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| processes | 当前用户可见的 JVM 进程列表。限制仅返回10条数据。 |
TDQS
Scored across 3 tools
Each tool targets a distinct JVM diagnostic area: garbage collection stats, thread snapshots, and heap object histograms. There is no meaningful overlap between these three concerns.
All tool names follow a consistent lowercase snake_case pattern using a domain prefix followed by a report type (gc_stat, thread_dump, heap_histogram). The naming convention is uniform and predictable.
Three tools is a tight, well-scoped set for a focused JVM diagnostics server. Each tool serves a distinct diagnostic purpose without unnecessary bloat.
Core JVM health diagnostics are covered for GC, threads, and heap usage. Minor gaps exist such as classloading or CPU/OS-level metrics, but the primary snapshot needs are addressed.