Skip to main content
Glama

jdx_annotated

Lists classes and members carrying a given annotation by type, '@Type(k=v)' predicate, or recipe alias, equivalent to annotation usages in JVM code.

Instructions

List classes/members carrying an annotation (issue #26). Query may be a type, '@Type(k=v)' use spelling, or a recipe alias (deprecated|forRemoval|test|junit5|junit4|bean). Equivalent to usages with kind=annotation.

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

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
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).
whereNoComma-separated annotation value predicates key=value (AND; e.g. forRemoval=true). Equivalent: query='@Type(k=v)'. Issue #26.
contextNoSnippet lines around each hit (default 0).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

A4.2/5.0
Behavior3/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. 'List' implies a read-style operation, and the query forms are useful, but the description does not disclose return shape, truncation behavior, or other operational details beyond what the schema already says.

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

Conciseness5/5

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

The description is three tight sentences. It front-loads the purpose, then explains query forms, then gives the usages equivalence, with no redundant wording.

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

Completeness4/5

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

The tool has seven parameters and no output schema, but the schema descriptions are fully populated. The description covers purpose, query syntax, and the closest equivalent, making it complete enough for correct invocation, though it could say more about result format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all seven parameters. The description adds value specifically for the required query parameter by naming annotation-specific forms such as type, '@Type(k=v)' use spelling, and recipe aliases.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'List classes/members carrying an annotation.' It also clarifies the query forms and says this is equivalent to usages with kind=annotation, which distinguishes it from the broader jdx_usages sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for using the tool: annotation-based listing, with accepted query spellings and recipe aliases. It stops short of explicit when-not guidance or a direct 'use X instead' alternative, but the equivalence to usages kind=annotation provides useful routing context.

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