Skip to main content
Glama

jdx_members

Lists members of a JVM type, including inherited members grouped by declaring type, with filters for kind, access, name, and declaration view.

Instructions

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "jdx_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoOnly members inherited from this supertype.
grepNoOnly members whose name matches this regex.
kindNoMember kind to list: method, field, ctor, property or all (default all).
sortNoRow order: kind (the default), name (flat name-first) or declaring.
viewNoDeclaration projection: kotlin (the default, true Kotlin declarations from @Metadata) or jvm (the raw JVM projection).
limitNoMaximum rows shown (default 50); the rest become a truncation footer.
queryYesThe symbol reference, type, pattern or glob the command asks about. Quote refs containing # or (). Empty only where the command allows it (ls, tree).
accessNoVisibility to list: public, protected, package, private or all (default: public + protected).
staticNoOnly static members (mutually exclusive with instance).
withDocNoInclude the first javadoc sentence per member.
declaredNoOnly members declared on this exact type (overrides the inherited default).
instanceNoOnly instance members (mutually exclusive with static).
workspaceNoNamed workspace to answer from (default: the workspace the server was started with). Stored workspaces only.
includeSyntheticNoInclude bridge/synthetic members, hidden by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the behavioral burden and does disclose two real traits: inherited members are included by default, and rows are grouped by declaring type. It says nothing about read-only nature, output row shape, or the truncation behavior that a large member list would hit.

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?

Two short sentences, front-loaded with the core purpose and followed by the default-behavior note. Nothing is redundant and nothing obvious is buried.

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 14-parameter tool with no output schema, the description covers purpose and the key default (inherited members, grouped by declaring type), and the schema handles the rest. The notable gap is that the agent gets no sense of the output row layout or pagination behavior, though the schema's limit/truncation note partly compensates.

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 coverage is 100%, so every parameter including the inherited/declared and sort axes is already documented. The description reinforces the inherited-by-default behavior that interacts with `declared` and `from`, but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 names a specific verb and resource ('List the members of a type') and adds a recognizable analogy ('the . completion equivalent'), so the agent knows exactly what comes back. It does not differentiate itself from plausible siblings such as jdx_outline or jdx_hierarchy, which keeps it from a 5.

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?

Usage is only implied through the completion analogy and the inherited-member default; there is no explicit statement of when to choose this over jdx_outline, jdx_hierarchy, or jdx_signature. The agent must infer the selection criteria from sibling names alone, which the description never addresses.

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