Skip to main content
Glama

jdx_literals

Search string constants in JVM bytecode and .properties resource keys/values by substring or Java regex to find literals across artifacts.

Instructions

Search string constants across bytecode roots (LDC loads and String field ConstantValue) and .properties resource keys/values. Substring by default; set regex=true for a Java regex.

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

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
limitNoMaximum rows shown (default 50); the rest become a truncation footer.
queryYesSubstring (or regex pattern) to find in string constants.
regexNoTreat query as a Java regex.
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.
ignoreCaseNoCase-insensitive substring match (ignored under regex; use (?i) there).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.7.0

TDQS

B3.4/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 burden. It discloses the search surface (bytecode LDC/ConstantValue plus .properties) and default substring behavior with escaping implied by regex=true, but says nothing about permissions, whether matching is per-artifact across a whole workspace, or result ordering/cost.

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 tight sentences, front-loaded with the search surface and followed by the matching-mode default. No filler, though a single clause on exclusions or workspace scope could have been added at little cost.

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?

A seven-parameter search tool with no annotations and no output schema is under-described: how results are grouped per artifact, how truncation interacts with limit, and how workspace selection behaves are all left implicit. The core capability is clear, but an agent must probe to understand output shape and cost.

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 all seven parameters are already documented in structured form; the description only reinforces the query/regex relationship. It adds no semantics beyond the schema, such as glob syntax for in/exclude or what a truncation footer looks like, so baseline 3 applies.

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?

Names a specific verb and highly specific resources: string constants from LDC loads, String field ConstantValue attributes, and .properties keys/values. This is far more precise than a sibling like jdx_search, though it doesn't explicitly name which sibling to use for other kinds of search.

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?

Gives the default matching mode and the regex opt-in, which implicitly tells the agent when to toggle regex=true. However, it offers no explicit when-to-use versus alternatives (e.g., jdx_search for general text, jdx_resources or jdx_show for resource files), leaving routing to inference.

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