DBJavaGenix

springboot_read_config

Reads Spring Boot project configuration files to detect base package. Supports YAML, properties, and Bootstrap configs with profile overlay and merging.

Instructions

Read Spring Boot project configuration (YAML/Properties/Bootstrap) and infer base package

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": "springboot_read_config"
  }
}

Input Schema

Name	Required	Description	Default
`project_path`	No	Optional explicit project root to scan
`active_profile`	No	Profile name to overlay (e.g. dev, prod)
`include_profiles`	No	Whether to collect all available profile files
`merge_strategy`	No	How to merge base and profile configs	overlay

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 26, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the action (read) and purpose (infer base package) without mentioning side effects, authorization needs, or performance characteristics. It does not clarify whether the tool accesses remote resources or has any destructive potential.

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 a single, well-formed sentence of 11 words with no redundancy. It is front-loaded with the primary verb and resource, making the purpose immediately clear.

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?

While the tool has 4 optional parameters and no output schema, the description lacks details about what 'infer base package' means or what the return value contains. For a tool with moderate complexity, additional context about expected output or behavior would be beneficial.

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 baseline is 3. The description does not add parameter-level meaning beyond what the schema already provides. For example, 'merge_strategy' enum values are not explained in context.

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 uses a specific verb ('Read') with a clear resource ('Spring Boot project configuration') and adds an additional purpose ('infer base package'). It distinguishes itself from siblings like springboot_validate_project and springboot_analyze_dependencies, which focus on validation and dependency analysis respectively.

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 prerequisites, typical scenarios, or when not to use it. The sibling tools list exists but the description lacks explicit context.

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