Skip to main content
Glama

jdx_callers

Find who calls a given JVM method or symbol, returning a depth-bounded call tree. Use exact mode to match invoke owners only, or override-aware matching by default.

Instructions

Call hierarchy in: who calls this method, as a depth-bounded tree. Override-aware by default; set exact=true for invoke-owner matching only.

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

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
depthNoHow many tree levels to walk (default 1).
exactNoMatch invoke owners exactly (no override / supertype expansion).
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).
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

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose two meaningful traits: results form a depth-bounded tree and matching expands overrides/supertypes unless exact is set. It says nothing about read-only safety, how truncation is reported, or the workspace-scoping behavior, all of which live only in 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?

Two short sentences, with the core purpose front-loaded and the override/exact contrast second. The opening fragment "Call hierarchy in:" is slightly terse, but no sentence is wasted.

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?

With no output schema, the description helpfully characterizes the response as a depth-bounded tree, and the schema fully documents all seven parameters. The remaining gap is that nothing signals the query-required constraint or the workspace default, which an agent only learns by reading the 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 coverage is 100%, so every one of the seven parameters is documented in structured form and baseline is 3. The description's only parameter reference restates exact in nearly the same words as the schema ("invoke-owner matching only" vs "Match invoke owners exactly"), adding no new meaning.

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 direction ("who calls this method") plus the return shape ("depth-bounded tree"), which is enough to distinguish it from an outbound-callee tool like jdx_calls. It stops short of naming any sibling explicitly, so an agent must infer the boundary against jdx_usages.

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?

Useful guidance exists for one decision point: the tool is override-aware by default and exact=true narrows to invoke-owner matching. There is no guidance on when to prefer this over jdx_usages or jdx_calls, nor any prerequisites (workspace, query quoting) mentioned in the description.

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