archprint
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| archprint_scanA | List the architecture rules this TypeScript repo already follows, with the evidence: each rule stated in plain words, whether it is AUTO (clears the confidence gate) or SUGGEST (short of it, worth review), how many files conform vs. break it, the files that break it, and the confidence. Read-only. |
| archprint_recommendA | Recommend an architecture rule set for this repo from its evidence and detected stack: what to enforce now, what the code already follows that archprint reports but does not write a rule for yet (reportOnly), what to review before enforcing, and what comparable repos commonly adopt that this repo does not yet. Read-only. |
| archprint_explainA | Explain the confidence-gate evidence behind one rule from archprint_scan, by its label (e.g. AP-002, env-access, or "lib !-> app"): its statement, gate status, conformance stats, and every file that breaks it. Read-only. |
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 3 tools
Each tool has a clearly distinct purpose: scan lists existing rules with evidence, recommend suggests a rule set, and explain drills into one rule from scan. There is no overlap in outputs or actions, and the descriptions make the boundaries explicit.
All tool names follow the same archprint_<verb> snake_case pattern with clear, consistent verbs (scan, recommend, explain). No deviations or mixed conventions.
Three tools are well-scoped for a read-only architecture analysis server, covering discovery, recommendation, and explanation without redundancy. Each tool earns its place and the set is not thin.
The surface covers listing existing rules, recommending a rule set, and explaining a single rule in detail, which is complete for a read-only advisor. A minor gap is the absence of a tool to export or apply rules, but that may be intentionally out of scope.