Skip to main content
Glama

jdx_implementors

Find classes and interfaces that implement or extend a specified type, including transitive implementors, to trace inheritance and usage across JVM code.

Instructions

Who implements this interface or extends this class, transitively.

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

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
depthNoHow many tree levels to walk (default 2147483647).
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).
directNoDirect implementors only.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations were supplied, so the description carries the full burden. 'Transitively' usefully discloses that the default walk is recursive, which explains the depth and direct parameters. However, it says nothing about read-only semantics, result ordering, or output shape for a 7-parameter query.

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?

One front-loaded sentence with zero filler; the core question is immediately clear. It is a bare fragment rather than structured prose, and slightly under-specified for a tool with seven parameters.

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 tool with no annotations and no output schema, the description should say more: whether results are grouped by implementor, whether the walk covers subclasses of subclasses only, and what happens at the depth limit. The richly documented schema covers inputs, but output and safety behavior are left entirely to inference.

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, which sets the baseline at 3. The single word 'transitively' does clarify the default behavior behind direct and depth, but adds no detail on query syntax or how 'in' and 'exclude' interact with the walk.

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?

States a specific verb-and-resource pair ('Who implements this interface or extends this class') and adds the scope modifier 'transitively'. The agent knows exactly what question the tool answers. It does not name or contrast any sibling (e.g., jdx_usages, jdx_callers), so it falls short of 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: 'interface or class' signals the intended target kind, and 'transitively' hints that a direct-only mode exists. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling query tools, leaving the agent to infer routing.

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