Skip to main content
Glama

jdx_outline

Lists declared members of a JVM type as one dense line per member, excluding inherited members so you can inspect a class's own methods, fields, and constructors.

Instructions

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

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

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

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses only that output is one dense line per member, excluding inherited members by default. It says nothing about truncation behavior, view projections, workspace selection, or the apparent tension between 'never inherited' and the `from` parameter that surfaces inherited members.

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?

A single terse sentence with no filler, and the key constraint is front-loaded. It is efficient but borders on under-specification given the tool's 13 parameters and filtering options.

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

Completeness2/5

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

For a 13-parameter tool with no annotations and no output schema, one fragment is far too thin. The agent must infer the tool's purpose relative to a large sibling set and derive all filtering, view, and truncation behavior from the schema alone.

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 all 13 parameters are already documented in the schema. The description adds no parameter-specific meaning beyond the default-exclusion of inherited members, leaving it at the baseline for fully documented schemas.

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

Purpose3/5

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

The description conveys the output shape (one dense line per declared member of a type) but never states a clear verb or resource, and the 'File Structure' prefix is vague. It does not distinguish this tool from close siblings such as jdx_members, jdx_ls, jdx_signature, or jdx_tree, so an agent cannot tell which to pick from the text alone.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no named alternative. The parenthetical '(never inherited)' hints at a scoping rule but does not explain when to choose outline over members or ls, nor when to use the `from` filter to include inherited members.

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