Skip to main content
Glama

jdx_show

Retrieve a type's declaration card, including kind, supertypes, source, and provenance, to inspect where and how a JVM symbol is defined.

Instructions

Go to declaration: the class card for a type (kind, supertypes, source, provenance).

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

Input Schema

NameRequiredDescriptionDefault
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.2/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 burden. It does disclose the returned field set (kind, supertypes, source, provenance), which is genuinely useful, but says nothing about behavior when the query resolves to a non-type symbol, when the type is unknown, or what "provenance" means for the caller.

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 dense sentence with the action front-loaded and the return payload in parentheses; nothing is wasted. The terse "class card" framing is compact but slightly jargon-y for an agent unfamiliar with the domain.

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 no annotations and no output schema, the description does double duty and partially succeeds by enumerating result fields. It still leaves gaps for a lookup tool: no mention of resolution failure behavior, no differentiation among the many sibling query tools, and no indication of how deep the supertypes walk goes.

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 both query and workspace are already documented in the schema, including the glob/quoting and workspace-default rules. The description only weakly reinforces this by framing query as a type, adding little beyond the schema baseline.

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?

"Go to declaration: the class card for a type" gives a concrete verb and a concrete result shape, and names the returned fields (kind, supertypes, source, provenance). That distinguishes it reasonably well from content-oriented siblings like jdx_source or jdx_body, though no sibling is named explicitly.

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 phrase "Go to declaration" implies an IDE-style navigate-to-definition action, which hints at when to reach for it, but there is no explicit statement of when to prefer it over jdx_source, jdx_signature, or jdx_hierarchy, and no stated exclusions.

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