Skip to main content
Glama

jdx_modules

List JPMS module-info descriptors across a workspace, including requires, exports, opens, uses and provides, and filter by module name, package, service or provider class.

Instructions

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).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jdx_modules"
  }
}

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
limitNoMaximum rows shown (default 50); the rest become a truncation footer.
queryNoOptional subject: package glob (ls), artifact glob (tree), service/provider substring (services), or module/package/service substring (modules). Empty lists everything.
regexNoTreat query as a Java regex.
excludeNoSkip matches from artifacts whose label matches this glob.
workspaceNoNamed workspace to answer from (default: the workspace the server was started with). Stored workspaces only.
ignoreCaseNoCase-insensitive substring match (ignored under regex; use (?i) there).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the burden; "List" signals a read-only scan and it discloses scope (whole workspace, all artifacts) plus what it deliberately does not read (META-INF/MANIFEST.MF). It stops short of describing row shape or the cost of a full-workspace scan, but the behavioral profile is largely clear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with purpose, then query semantics, then the sibling exclusion. No filler and nothing repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter read tool with no output schema, the description covers purpose, matching semantics, scope, and the nearest alternative, which is most of what an agent needs. It does not say what a returned row looks like (file location plus directive set) or that results span multiple artifacts, which would close the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds module-specific meaning beyond the schema: it explains what a query matches against (module name, exported/opened package, service, provider class), whereas the schema's query text is generic cross-tool language. The remaining parameters (in, exclude, limit, regex, workspace, ignoreCase) are left to their own schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List JPMS module-info descriptors across the workspace" names a specific verb and resource, and the parenthetical (requires, exports, opens, uses, provides) pins down exactly what information is surfaced. It also explicitly distinguishes itself from the nearest sibling ("use jdx_manifest for that"), so an agent can choose without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states both operating modes (omit query = list every module; supply query = match against module name, exported/opened package, uses/provides service, or provider class) and names an explicit exclusion with the correct alternative for manifest data. That is when-to-use, when-not-to-use, and the alternative in three sentences.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.