Skip to main content
Glama

jdx_resolve

Resolves short JVM symbol references into copy-pasteable candidates, so you can identify ambiguous names from a query, type, pattern, or glob.

Instructions

What is this symbol? Short-name resolution with copy-pasteable candidates.

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

Input Schema

NameRequiredDescriptionDefault
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).
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.1/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 burden. It does reveal that the result is a set of candidate references intended to be copy-pasted, which is useful output context, but it omits whether resolution is read-only, what happens when nothing matches, and how ambiguity is ranked.

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 fragments, front-loaded with the core question, with no filler. The terseness borders on underspecification, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three fully documented parameters and no output schema, the description covers the core purpose but leaves gaps around match ordering, ambiguity handling, and the truncation behavior implied by the limit parameter. Adequate, not complete.

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 query, limit, and workspace are already well documented in the schema. The description adds no parameter-level meaning (e.g., how glob patterns behave or how workspace selection affects results), so the baseline of 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 phrase 'short-name resolution with copy-pasteable candidates' names a specific operation (resolving a short symbol name to candidates), which is clearer than a tautology. However, it does not distinguish this from siblings such as jdx_search, jdx_show, or jdx_signature, so an agent cannot confidently pick it over them from the description alone.

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?

The opening question 'What is this symbol?' implies the scenario: you have an ambiguous or partial symbol reference and need disambiguation. There is no explicit when-not guidance and no named alternative, so the routing signal is only implied.

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