jar-inspector-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jar_overviewA | Summarize a Java archive: manifest, size, packages, class count, and whether sources are attached. Start here when you meet an unfamiliar jar, instead of unzipping it or listing every entry. Args:
jar: Path to a .jar/.war/.aar/.zip, an exploded classes directory, or a
nested archive such as |
| jar_listA | List entries in an archive, filtered by glob and kind. Prefer this over Args:
jar: Archive path, classes directory, or |
| jar_find_classA | Find classes in an archive by simple name, fully-qualified name or glob. Use this to turn "where does Args:
jar: Archive path, classes directory, or |
| jar_class_outlineA | Show a class's API: declaration, annotations, fields and method signatures. This is the cheap alternative to decompiling or reading source. Signatures
keep generics, parameter names (when compiled with Args:
jar: Archive path, classes directory, or |
| jar_read_sourceA | Read attached Java/Kotlin source for a class, one line window at a time. Looks inside the archive itself, then the matching Args:
jar: Archive path, classes directory, or |
| jar_read_entryA | Read one text entry from an archive: MANIFEST, service files, XML, config. Prefer this over Args:
jar: Archive path, classes directory, or |
| jar_searchA | Grep text and source entries inside an archive, returning matching lines. Use it to find a property key, a bean name, an SQL fragment or a log
message without extracting anything. With Args:
jar: Archive path, classes directory, or |
| jar_class_dependenciesA | List the classes a compiled class references, split into internal and external. Useful for tracing what a class actually touches, and for spotting which dependency supplies a type, without decompiling anything. Args:
jar: Archive path, classes directory, or |
| jar_disassembleA | Disassemble one method's bytecode with Reach for this only when the API outline and the source are not enough --
for example when checking what a method compiles to, or reading a class
that has no sources attached. Always pass Args:
jar: Archive path or classes directory (nested |
| jar_findA | Find jar files on this machine by name: build output, Maven repo, Gradle cache. Use it to turn "the Jackson databind jar" into a path you can pass to the other tools. Args:
query: Part of the file name, or a glob such as |
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 10 tools
Each tool targets a distinct inspection task: overview, listing, class lookup, API outline, source reading, entry reading, search, dependency analysis, disassembly, and jar discovery. There is no meaningful overlap that would make an agent likely to pick the wrong tool.
All tools share the jar_ prefix, which helps, but the grammatical pattern is mixed: jar_list and jar_search are bare verbs, jar_find_class and jar_read_source are verb_noun, while jar_overview and jar_class_outline are noun phrases. The names are readable but not consistently verb_noun.
Ten tools is well within the ideal range and each tool covers a distinct facet of archive inspection. The count feels neither bloated nor thin for the stated purpose.
The read-only jar inspection domain is covered thoroughly: overview, listing, class lookup, API outline, source reading, arbitrary text entries, grep-like search, class dependency analysis, bytecode disassembly, and locating jars on disk. An agent can move from finding a jar to reading its source or bytecode without obvious dead ends.