Skip to main content
Glama

jdx_ls

List packages from external libraries in a workspace and filter results by package query to browse available dependencies.

Instructions

External library browser: packages in the workspace roots.

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

Input Schema

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

No annotations are supplied, so the description carries the full behavioral burden, and it delivers almost nothing: it does not state that the operation is read-only, what the output looks like, how truncation behaves, or whether an unknown workspace errors or falls back. "External library browser" is the only contextual hint, and it is thin for a tool with zero annotation coverage.

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?

A single short sentence with no filler, so it is certainly concise, but it is under-specified rather than efficient — the brevity comes at the cost of scope and differentiation. There is no front-loaded statement of what the agent gets back.

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 three-parameter listing tool with no annotations and no output schema, the description should at minimum clarify scope, return shape, and overlap with sibling listing tools. It does none of these, leaving the agent to infer behavior from the parameter 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 three parameters (limit, query, workspace) are documented in the schema, and the baseline is 3. The description adds no meaning beyond the schema and in fact understates the query parameter's documented breadth by framing the tool as packages-only.

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 says it is an "External library browser" that lists "packages in the workspace roots," which gives a rough verb+resource sense. However, it is scoped only to packages, while the schema's query parameter claims this tool also handles artifact globs, service/provider substrings, and module substrings — so the stated purpose is narrower than the tool's actual surface. It also gives no differentiation from siblings like jdx_tree, jdx_modules, or jdx_services.

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 statement of when to use this tool versus the many overlapping listing siblings. No prerequisites, no exclusions, and no routing guidance for choosing between jdx_ls, jdx_tree, jdx_services, and jdx_modules when an agent wants a directory-style listing.

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