Skip to main content
Glama

jdx_manifest

List META-INF/MANIFEST.MF attributes across workspace JARs, optionally per entry, and query by attribute name or value to inspect manifest metadata.

Instructions

List META-INF/MANIFEST.MF attributes across the workspace jars. Default: main-section attributes. Set entries=true for per-entry (JarEntry) attributes instead. Omit query to list every attribute in that section; with a query, match the attribute name or value (and entry path when entries=true). Does not extract resource file bytes (use jdx_resources with cat=true for text).

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

Input Schema

NameRequiredDescriptionDefault
inNoOnly matches from artifacts whose label matches this glob.
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.
regexNoTreat query as a Java regex.
entriesNoList per-entry (JarEntry) attributes instead of main-section attributes.
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

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden and does well: it discloses default scope, the mode switch, matching semantics (name, value, and entry path), and what the tool does not do. It omits ordering, behavior when jars are missing or unreadable, and any note about the truncation footer beyond what the schema 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?

Four compact sentences, front-loaded with scope then modes then exclusion; no filler. The ordering (default, alternative, query semantics, boundary) follows how an agent would build a call.

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?

For an 8-parameter read tool with no output schema and no annotations, the definition covers what an agent needs to choose a mode and construct a query. It leaves the result shape and the interaction with limit/truncation to the schema and caller inference.

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 description coverage is 100%, so the baseline is 3; the description earns more by explaining how entries interacts with query matching (entry path is matched only when entries=true). It still says nothing about in/exclude glob labels, workspace selection, or ignoreCase behavior beyond the schema text.

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 opens with a precise verb and resource: 'List META-INF/MANIFEST.MF attributes across the workspace jars.' It also names the boundary against the closest sibling ('use jdx_resources with cat=true for text'), so an agent can select it without opening other tools.

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

Usage Guidelines5/5

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

It spells out the default mode (main-section attributes), the switch to per-entry mode via entries=true, and the meaning of omitting versus supplying a query. It explicitly excludes resource-byte extraction and routes that case to jdx_resources.

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