Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

jdx — an IDE for AI agents: Java/Kotlin structure, sources, usages and call graphs, one precise question per tool. Every answer carries provenance; ambiguous refs list candidates instead of guessing.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
jdx_showB

Go to declaration: the class card for a type (kind, supertypes, source, provenance).

jdx_membersA

List the members of a type — the '.' completion equivalent. Inherited members are included by default, grouped by declaring type.

jdx_outlineC

File Structure: one dense line per member declared on a type (never inherited).

jdx_bodyB

Open the method: the source body of one member, sliced verbatim with provenance.

jdx_sourceC

Open the file: whole source for a type, or a slice of it, with provenance.

jdx_signatureC

Parameter info: one signature line per overload, with real parameter names.

jdx_docB

Quick documentation for a type or member, falling back to the nearest documenting supertype like IntelliJ quick-doc.

jdx_searchA

Search symbols by glob, regex or fuzzy name. Default kind=all covers types, packages and modules; pass kind=method|field to scan members. A default-kind miss hints at --kind method.

jdx_resolveB

What is this symbol? Short-name resolution with copy-pasteable candidates.

jdx_lsC

External library browser: packages in the workspace roots.

jdx_treeC

External library browser: artifacts and their package trees.

jdx_usagesB

Find usages of a type or member across the workspace jars and source dirs. With kind=annotation, query may use annotation-use spelling '@Type(k=v)' (issue #26).

jdx_annotatedA

List classes/members carrying an annotation (issue #26). Query may be a type, '@Type(k=v)' use spelling, or a recipe alias (deprecated|forRemoval|test|junit5|junit4|bean). Equivalent to usages with kind=annotation.

jdx_hierarchyC

Type hierarchy: supertypes upward and subtypes downward across the workspace.

jdx_implementorsB

Who implements this interface or extends this class, transitively.

jdx_callersA

Call hierarchy in: who calls this method, as a depth-bounded tree. Override-aware by default; set exact=true for invoke-owner matching only.

jdx_callsC

Call hierarchy out: what this method calls, as a depth-bounded tree.

jdx_samplesB

How is this symbol really used? Ranked call sites with source snippets as evidence.

jdx_literalsB

Search string constants across bytecode roots (LDC loads and String field ConstantValue) and .properties resource keys/values. Substring by default; set regex=true for a Java regex.

jdx_servicesA

List META-INF/services SPI registrations across the workspace jars. Omit query to list every registration; with a query, match the service interface FQN or a provider class FQN. Does not read module-info provides (use jdx_modules for that).

jdx_modulesA

List JPMS module-info descriptors across the workspace (requires, exports, opens, uses, provides). Omit query to list every module; with a query, match the module name, an exported/opened package, a uses/provides service, or a provider class. Does not read META-INF/MANIFEST.MF attributes (use jdx_manifest for that).

jdx_manifestA

List META-INF/MANIFEST.MF attributes across the workspace jars. Default: main-section attributes. Set entries=true for per-entry (JarEntry) attributes instead. Omit query to list every attribute in that section; with a query, match the attribute name or value (and entry path when entries=true). Does not extract resource file bytes (use jdx_resources with cat=true for text).

jdx_resourcesA

List non-class resource paths across the workspace jars (META-INF, .properties, versioned META-INF/versions/… copies, …). Omit query to list every resource; with a query, match the entry path. Pass cat=true to print the unique match's text contents (binary payloads refuse to dump bytes; ambiguous matches exit 2). maxLines caps --cat text lines (default 200).

jdx_diffA

What changed between two artifacts? Public-API diff with named binary-compatibility rules (MEMBER_REMOVED, RETURN_TYPE_CHANGED, ...), most breaking first. query is the OLD artifact and new the candidate; each is a jar, class dir, glob, or Maven coordinate. Exits 0 whenever the comparison ran.

jdx_versionB

The jdx version this server was built as.

jdx_doctorA

Environment report. The server refuses this over MCP — it describes the server's machine, not the client's — run jdx doctor in a shell instead.

jdx_healthB

Liveness probe: uptime, workspace served and queries answered.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 27 tools

Disambiguation3/5

Most tools have a clearly stated niche, and descriptions proactively cross-reference siblings (e.g. services vs modules vs manifest each name the tool to use instead). However there are real overlaps: jdx_annotated is explicitly 'equivalent to usages with kind=annotation', jdx_hierarchy's downward direction largely duplicates jdx_implementors, jdx_members vs jdx_outline differ only by inheritance handling, and jdx_ls vs jdx_tree both open with 'External library browser'. An agent can recover from the rich descriptions, but misselection is likely in those pairs.

Naming Consistency5/5

Every tool uses the identical `jdx_` prefix plus a single lowercase token (tree, resolve, members, callers, diff...), with no camelCase or separator drift anywhere. The verb/noun mix is intentional and readable (verbs like resolve/search/show/diff, nouns like members/hierarchy), so the convention is fully predictable.

Tool Count3/5

27 tools exceeds the comfortable range, and a few don't earn their place: jdx_doctor is explicitly non-functional over MCP, and jdx_version/jdx_health are thin meta probes. The remaining surface is broad but genuinely differentiated across navigation, relationships, and bytecode/artifact inspection, so it's heavy rather than bloated.

Completeness4/5

For a read-only JVM code-intelligence server the lifecycle is well covered: symbol search, short-name resolution, declarations, members, bodies, source slices, signatures, docs, usages, hierarchy, call graphs, samples, literals, SPI/JPMS/manifest/resource scanning, and artifact diffing. Gaps are minor for the stated purpose (no type-of-expression or diagnostics/compile-check operation), and read-only operation means no write tools are expected.

Maintenance

ActivityActive
ResponsivenessNo recent community issues