Skip to main content
Glama

jdx_tree

Browse external library artifacts and package trees, control tree depth and row limits, and annotate nodes with class counts.

Instructions

External library browser: artifacts and their package trees.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jdx_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoTree depth (default 8).
limitNoMaximum rows shown (default 50); the rest become a truncation footer.
queryNoOptional subject: package glob (ls), artifact glob (tree), service/provider substring (services), or module/package/service substring (modules). Empty lists everything.
countsNoAnnotate nodes with class counts.
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

C2.5/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 burden and discloses almost nothing: not whether the tool is read-only, not what the tree output looks like, not how truncation is signalled, and not any workspace/permission implications. Only the phrase 'browser' weakly implies a non-mutating inspection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence fragment with no wasted words, but that is brevity by omission rather than disciplined structure. There is no front-loaded verb or subject, so the reader cannot anchor on what the tool returns.

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?

A five-parameter tool with no annotations and no output schema needs the description to explain the tree structure, truncation-footer behavior, and mode switching via query. None of that is present, leaving the agent under-equipped for anything beyond a blind default call.

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 in the schema, including defaults for depth, limit, and workspace. The description adds no additional semantics about how depth, counts, or the polymorphic query modes interact, so the baseline 3 applies.

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 fragment 'External library browser: artifacts and their package trees' names the resource domain (artifacts and their dependency/package trees) but gives no verb or action, so the agent must infer that it renders a tree view. It also does not distinguish this from siblings such as jdx_ls, jdx_modules, jdx_services, or jdx_resources, which the query parameter suggests overlap with.

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 guidance on when to pick this tool over jdx_ls, jdx_modules, jdx_services, or jdx_resources, despite the query parameter's schema text hinting that those modes are partly absorbed here. The agent is left to reverse-engineer usage from parameter descriptions.

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