help
Explains what a running Jeffrey Microscope can investigate and how to get there — the areas a JFR recording or a heap dump can answer (CPU, wall-clock, allocation, locks, requests and outbound calls, the database, I/O, exceptions, GC and pauses, JIT, threads, native memory, the container, leaks, and a heap dump's contents, retention and waste), what each needs recorded, which skill takes each, and which profiles are here now. Use whenever the user asks what Jeffrey or Microscope can do, what they can investigate or ask, which areas there are, what to record so a question can be answered, how to start, or says "help" about Jeffrey, before any profile is chosen. For a profile already named with an open question, analyze-jfr's menu applies directly.
Pinned to revision e864e622df0d, so it is the text this page describes rather than whatever the author pushed since.
Pre-approved tools experimental
Experimental field. Support varies between clients, so this list is what the author declared, not what your client will enforce.
- mcp__plugin_microscope_jeffrey__*
- mcp__jeffrey__*
Files
Every link opens the file at its source, pinned to the revision this page describes.