sleuths-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_thread_dumpA | Parse a jstack / jcmd Thread.print thread dump text and return: total thread count, state distribution, deadlocked threads, hot locks, top frames. |
| parse_exception_logA | Aggregate raw exception logs: group by exception type, count occurrences, extract root cause (Caused-by chain) and first frame. Returns a structured summary you can use to tell which error dominates and where it originates. |
| analyze_gc_logB | Parse JVM GC logs and return: total GC events, Young/Full counts, average and max pause time, memory trend, and whether Full GC is frequent. |
| analyze_heap_histoA | Parse jmap -histo output: top classes by bytes, total heap, and suspected application-level memory leaks (non-JDK classes taking >5% heap). |
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 4 tools
Each tool targets a distinct JVM diagnostic artifact: thread dumps, exception logs, GC logs, and heap histograms. There is no meaningful overlap in purpose, so an agent can select the right tool from the input type alone.
All names follow a consistent snake_case verb_noun pattern. The verbs alternate between analyze and parse, but both are semantically appropriate and the structure remains highly predictable.
Four tools is well-scoped for a focused JVM diagnostics server. Each tool covers a distinct and commonly needed artifact, so none feels redundant or out of place.
The surface covers the core JVM troubleshooting artifacts: thread dumps, exception aggregation, GC logs, and heap histograms. Minor gaps exist around heap dump analysis and JFR-style profiling, but the main diagnostic workflows are supported.