Skip to main content
Glama

jdx_resources

List non-class resource paths in workspace jars and print a unique matching resource's text contents to inspect META-INF, properties, or versioned copies.

Instructions

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

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_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
catNoPrint the unique matching resource's text instead of listing paths. Requires a query; exits 2 when more than one path matches.
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.
maxLinesNoMaximum text lines shown under cat=true (default 200).
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

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that binary payloads refuse to dump bytes, that ambiguous cat matches exit 2, and that maxLines defaults to 200. It still omits the shape of the listing output (are full paths printed? grouped by artifact?) and whether workspace scoping constrains reads, but overall it conveys real behavioral traits rather than restating the schema.

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

Conciseness4/5

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

Four short sentences, front-loaded with the purpose followed by mode selection and the cat behavior — no padding. The only inefficiency is mild duplication between 'ambiguous matches exit 2' in sentence three and the schema's own exit-2 note, but it keeps related behavior together.

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 9-parameter, read-only query tool with full schema coverage and no output schema, the definition covers purpose, mode selection, cat semantics, and failure modes adequately. The remaining gap is that it never sketches what a listing returns (path form, grouping, truncation footer content), which matters somewhat since there is no output schema.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented in structured form, making 3 the baseline. The description adds modest value by tying cat and maxLines together (--cat text lines, default 200) and noting ambiguity causes exit 2, but the other seven parameters (in, exclude, regex, ignoreCase, limit, workspace) receive no added meaning beyond their schema text.

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

Purpose4/5

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

The description opens with a specific verb and resource — 'List non-class resource paths across the workspace jars' — and gives concrete examples (META-INF, .properties, versioned META-INF/versions/ copies). The 'non-class' qualifier implicitly separates it from a class-listing sibling, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

It explains the two modes of operation well: omit query to list everything, supply a query to match entry paths, and use cat=true to dump a unique match. However, this is all parameter-level instruction; there is no guidance on when to choose this tool over jdx_ls, jdx_ls-style class listing, or jdx_show, and no stated prerequisites or exclusions.

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