Skip to main content
Glama

jdx_calls

Builds a depth-bounded call hierarchy tree showing what a symbol or method calls, with filters for workspace, artifacts, depth, and external-only callees.

Instructions

Call hierarchy out: what this method calls, as a depth-bounded tree.

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

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
depthNoHow many tree levels to walk (default 1).
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.
externalOnlyNoPrune callees in the target's own artifact (dependency view).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses only that traversal is depth-bounded and returns a tree; it says nothing about defaults beyond what the schema already shows, truncation behavior, workspace resolution, or cost of deep walks.

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 compact sentence with the key concept (outbound, depth-bounded tree) front-loaded and zero filler. The colon construction and phrase "hierarchy out" are slightly cryptic but not wasteful.

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 seven-parameter, unannotated tool with no output schema, one sentence is thin. An agent gets the direction and the tree shape but not the operational context — how depth and limit interact, what a truncation footer means in practice, or what workspace scoping implies.

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 seven parameters are already documented in structured form. The phrase "depth-bounded tree" reinforces the depth parameter's effect on output shape but adds no syntax, defaults, or interactions beyond the schema.

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?

"Call hierarchy out: what this method calls" states a specific direction and resource — outbound callees of a method — which is concrete enough to act on. It does not explicitly name the inverse sibling (jdx_callers) or jdx_hierarchy, so differentiation is left to inference from the word "out".

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, no statement of prerequisites, and no named alternative for the inbound-direction case. The agent must infer from the word "out" alone that jdx_callers is the counterpart.

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