Skip to main content
Glama

Analyze Spring Boot Project

analyze_springboot_project
Read-onlyIdempotent

Inspect a Spring Boot project to identify missing layers, configuration gaps, and dependency issues so you can fix structural problems before deployment.

Instructions

Inspect a Spring Boot project and report missing layers, configuration and dependency issues.

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

Input Schema

NameRequiredDescriptionDefault
projectPathNoPath to the Spring Boot project (default: working directory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety and side-effect behavior are covered structurally. The description adds the useful detail that it reports missing layers plus configuration and dependency problems, but says nothing about report depth, whether it executes builds, or how long a scan takes.

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?

One front-loaded sentence with no filler, and the analyzed resource leads before the findings list. The trailing list is slightly compressed ("missing layers, configuration and dependency issues") and could be read as one or three categories, but nothing is wasted.

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?

For a read-only, single-optional-parameter analyzer this is close to sufficient, and the absence of an output schema means return values need not be described. However, "missing layers" is left undefined, and there is no hint about the shape or scope of the report an agent will receive, which matters when the whole purpose is producing a diagnostic report.

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?

With a single optional parameter at 100% schema description coverage, the schema already explains projectPath and its default of the working directory. The description adds no further meaning such as expected path format, whether relative paths are resolved, or behavior when the path is not a Spring Boot project.

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?

"Inspect a Spring Boot project and report missing layers, configuration and dependency issues" gives a concrete verb (inspect), a concrete resource (Spring Boot project), and enumerates the classes of findings. It is clear what the tool does, but it never distinguishes itself from sibling analyzers such as project_diagnostic, analyze_code, or fix_maven_dependencies, leaving overlap unresolved.

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?

There is no statement of when to use this tool versus the many sibling analysis tools, no prerequisites, and no exclusions. An agent must infer from the name alone that this is the Spring Boot-specific diagnostic path rather than the generic project_diagnostic.

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