MMI Architecture Analyzer
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_layeringB | Analyzes Clean Architecture layering violations in a C# project. Checks if Domain/Application/Infrastructure layers follow dependency rules. |
| analyze_encapsulationC | Analyzes encapsulation quality by checking public vs internal visibility of classes, interfaces, and records. Identifies over-exposed types that should be internal. |
| analyze_abstractionC | Analyzes separation of abstraction levels. Detects mixing of business logic (Domain/Application) with technical details (SQL, HTTP, File I/O). Identifies violations of clean separation. |
| analyze_mmiB | Complete MMI (Modularity Maturity Index) analysis. Runs all three dimensions: Layering (Dimension 2), Encapsulation (Dimension 5), and Abstraction Levels (Dimension 8). Provides overall architecture quality score. |
| start_monitoringB | Starts continuous MMI monitoring for a C# project. Watches .cs files and automatically analyzes on changes. Stores score history over time. |
| stop_monitoringB | Stops MMI monitoring for a project. Preserves history. |
| get_monitoring_statusB | Shows status of all monitored projects with current scores and trends. |
| visualize_architectureC | Generate interactive architecture heatmap visualization with D3.js. Shows files as nodes colored by score (green=good, red=critical), dependencies as links, violations highlighted. Click nodes to see details. |
| analyze_cyclesB | Analyzes circular dependencies (cycles) in the codebase. Detects files that depend on each other in a circular way, which violates good architecture principles. Critical when Domain layer is involved. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current MMI Scores | Current scores of all monitored projects |
| MMI Summary | Quick overview of all monitored projects with status |
TDQS
Scored across 9 tools
Most tools have distinct purposes, such as analyze_abstraction for abstraction levels and analyze_cycles for circular dependencies, but analyze_mmi overlaps by running multiple analyses that other tools handle individually, which could cause confusion in tool selection. The monitoring tools (get_monitoring_status, start_monitoring, stop_monitoring) are clearly separate from analysis tools, reducing overall ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case, such as analyze_abstraction, get_monitoring_status, and visualize_architecture. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions across the nine tools.
With 9 tools, the count is well-scoped for an architecture analyzer server, covering analysis, monitoring, and visualization aspects without being overwhelming. Each tool serves a clear role, such as specific analyses or monitoring controls, making the set appropriately sized for the domain.
The tool set provides comprehensive coverage for architecture analysis, including specific checks (e.g., layering, encapsulation), overall scoring (analyze_mmi), monitoring lifecycle (start/stop/get status), and visualization. A minor gap is the lack of tools for fixing or suggesting corrections for identified violations, but agents can work around this by using analysis results to guide manual improvements.