archiet-xray
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| directory | Yes | Path to the repository to analyze |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| xray_scanA | Scan the repository and build the architecture model (routes, entities, tasks, module dependency graph, findings). Run once at session start and after structural changes. |
| arch_summaryA | Compact architecture summary: modules, route prefixes, domain entities, hotspots, visibility score. Use this as ground truth for where things live before searching the codebase. |
| blast_radiusA | Given a file or top-level module path, report what depends on it (fan-in), what it depends on (fan-out), and the routes/entities it contains. Call BEFORE editing anything load-bearing. |
| boundary_findingsB | Deterministic risk findings: hardcoded secrets, raw SQL bypassing the ORM, auth tokens in localStorage, routes without auth guards. |
| production_readinessA | Score the repo's production readiness 0-100 across 8 deterministic dimensions (auth coverage, secrets hygiene, client token storage, data-layer discipline, test footprint, migration discipline, ops readiness, docs/API contract) with per-dimension evidence and the top fixes ranked by points lost. Same repo always scores the same. |
| generate_diagramsA | Generate architecture diagrams as Mermaid sources: module dependency graph, domain-model ER diagram, and HTTP route map. Also writes .archiet/diagrams/ (3 .mmd files + a self-contained HTML viewer). Paste the Mermaid into any README/wiki — GitHub, GitLab, Notion and VS Code render it natively. |
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 6 tools
Each tool targets a distinct concern: scanning, summarizing, dependency analysis, risk findings, scoring, and diagram generation. No two tools overlap in purpose, and descriptions reinforce their boundaries.
All tool names use lowercase snake_case, creating a uniform style. Although not all follow a strict verb_noun pattern, the naming convention is consistent across the set.
With 6 tools, the server is well-scoped for architecture analysis. Each tool addresses a core need, and the count is appropriate.
The set covers the full workflow from scanning the codebase to generating summaries, analyzing dependencies, surfacing findings, scoring readiness, and producing diagrams. No obvious gaps for an architecture analysis tool.