Maven Decoder MCP Server

Overview Schema Source Related Servers Discussions Admin

extract_class_info

Inspect Java classes in a JAR file using Maven coordinates, with regex filtering and optional inclusion of fields, methods, and bytecode.

Instructions

Get detailed information about Java classes in a jar

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": {
      "group_id": "<group_id>",
      "artifact_id": "<artifact_id>",
      "version": "<version>"
    },
    "name": "extract_class_info"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number for pagination
`version`	Yes	Maven version
`group_id`	Yes	Maven group ID
`artifact_id`	Yes	Maven artifact ID
`class_pattern`	No	Pattern to match class names (regex supported)
`include_fields`	No	Include field information
`items_per_page`	No	Items per page
`include_methods`	No	Include method signatures
`include_bytecode`	No	Include verbose javap bytecode output for matched classes
`summarize_large_content`	No	Summarize large content automatically

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.0Sep 9, 2026

TDQS

C2.9/5.0

Behavior2/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 of behavioral disclosure. It does not mention pagination, defaults like summarize_large_content, output format, or whether the operation is read-only. The description is generic and adds little beyond the tool name.

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?

The description is a single, front-loaded sentence with no redundant words. It is efficient, but it is also generic and could have included a brief mention of the Maven coordinate requirement without being verbose.

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

Completeness2/5

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

For a tool with 10 parameters, 3 required fields, no output schema, and no annotations, the description is too minimal. It leaves out context about expected return values, pagination behavior, and when to choose this tool among many overlapping siblings, making it hard for an agent to invoke it confidently.

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 the input schema fully documents all 10 parameters. The description adds no extra meaning about parameters, interactions, or defaults, so the baseline score of 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?

The description uses a specific verb ('Get') and identifies the resource ('detailed information about Java classes in a jar'). It is clear, but it does not differentiate among siblings like search_classes, analyze_jar_structure, or extract_method_info, so it is not a 5.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites (such as Maven coordinates), or that it might be better for detailed class inspection while other siblings handle searching or method extraction.

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

Deploy Server