spring-mosaic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| detect_spring_contextA | Detect Spring Boot / Java version, build tool, and modules. Call first. |
| list_quality_domainsA | Index of Java/Spring quality domains. Call first to discover what to fetch. |
| get_quality_guideC | Fetch ONE quality guide. spring-boot is version-scoped (boot2 vs boot3). |
| explain_patternC | Deep-dive on a Spring/Java topic (jpa, rest, security, transactions, etc.). |
| get_pr_review_briefC | Minimal PR review brief: review format + anti-patterns. |
| get_review_sections_for_diffC | Return only quality sections relevant to changed file types. |
| review_pr_diffD | PR review orchestration: changed files, extensions, and review steps. |
| review_architectureC | Architecture checklist for a Java/Spring diff. |
| scan_violationsC | Heuristic scan of Java/Kotlin source for common Spring anti-patterns. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Tools are mostly distinct with clear purposes. Some overlap exists between PR review tools (e.g., get_pr_review_brief vs review_pr_diff), but descriptions differentiate them effectively.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., detect_spring_context, list_quality_domains), making them predictable and easy to use.
With 9 tools, the server is well-scoped for its purpose (Spring/Java quality and PR review). No tool feels unnecessary, and the count is appropriate for the domain.
The tool set covers the full lifecycle of quality analysis: detection (detect_spring_context), exploration (list_quality_domains, get_quality_guide, explain_pattern), and PR review (brief, sections, orchestration, architecture, scanning). No obvious gaps.