Repo Test Architect
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 |
|---|---|
| analyze_repositoryA | Start here for an unfamiliar repository or a general test-architecture review. Detect and audit all project roots once, then return the complete deterministic summary, blockers, findings, ranking, plan, execution hints, verification commands, and stats. Prefer this over audit_repo unless one project root and adapter were explicitly selected. |
| list_adaptersA | List registered language adapters available to audit repositories. |
| list_project_detection_rulesA | List deterministic project marker rules and ignored directories used during project detection. |
| detect_projectsA | Discover project roots, support status, and matching adapters without auditing source targets. Use this when project boundaries are needed before a specialized workflow; use analyze_repository for a complete review. Reads local repository markers and returns project-detection/v1 without executing tests or writing files. |
| audit_projectsA | Return raw per-project audit artifacts for all detected supported roots and report unsupported roots. Use when a downstream specialist tool needs project-audits/v1; for a complete first-pass review, prefer analyze_repository. |
| summarize_project_auditsA | Summarize an existing project-audits/v1 artifact. Use only when a compact coverage view is needed separately; analyze_repository already includes this result. |
| rank_project_candidatesA | Rank candidates from an existing project-audits/v1 artifact while preserving project identity. analyze_repository already includes this result. |
| generate_project_test_planA | Generate a project-aware plan from an existing project-audits/v1 artifact. analyze_repository already includes this result. |
| collect_project_findingsA | Collect concise top findings from an existing project-audits/v1 artifact. analyze_repository already includes this result. |
| analyze_project_test_placementA | Derive advisory test-placement findings across an existing project-audits/v1 artifact while preserving project identity. Use this for multiple audited projects; use analyze_test_placement for one audit/v1 artifact. Does not rescan the repository, execute tests, or create, move, or modify files. |
| collect_project_statsA | Aggregate coverage, counts, risk and signal distributions, frameworks, and adapter usage from an existing project-audits/v1 artifact. Use this for separate reporting or comparisons; analyze_repository already includes the same stats. Returns project-stats/v1 without rescanning the repository, executing tests, or writing files. |
| audit_repoA | Audit one explicitly selected project root and return audit/v1. Use only when the caller selected a single adapter or project boundary; adapterId defaults to javascript. For an unfamiliar or complete repository review, use analyze_repository. |
| get_audit_graphA | Validate and return an existing audit/v1 artifact unchanged; this does not scan a repository. Use audit_repo or analyze_repository for repository discovery. |
| generate_test_planA | Create a deterministic plan/v1 from an existing single-project audit/v1 artifact. Use this after audit_repo, optionally selecting one exact plan item; use generate_project_test_plan for multiple audited projects. Does not rescan the repository, execute tests, or generate or write test code. |
| get_plan_execution_hintsA | Derive provider-neutral execution, context, parallel-safety, and repository-reasoning hints from a plan without invoking models or subagents. |
| explain_targetA | Explain the evidence, risk, testability, and recommendation for one target in an existing audit/v1 artifact. Use this after audit_repo or audit_projects when one target needs detail beyond the audit summary. Returns target-explanation/v1 without rescanning the repository, executing tests, or writing files. |
| rank_test_candidatesB | Rank testable audit targets by risk reduction and maintenance cost. |
| analyze_test_placementA | Derive advisory test-placement findings from an existing single-project audit/v1 artifact. Use this for one audited project; use analyze_project_test_placement for a project-audits/v1 artifact. Does not rescan the repository, execute tests, or create, move, or modify files. |
| generate_selected_testA | Return a structured deferred result. This tool does not generate or write test code while native generation remains disabled. |
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 19 tools
The set contains many overlapping artifact-consumption tools: analyze_repository subsumes several specialist outputs, and project-wide vs single-audit variants mirror each other. The long descriptions explicitly steer callers, but boundaries remain fuzzy enough that misselection is likely.
Almost all tools use snake_case verb_noun naming, making the surface predictable. Minor deviations exist, such as audit_repo vs analyze_repository and project-qualified vs unqualified variants.
19 tools is heavy for a repository test-architecture review server, and several tools only expose slices already included in analyze_repository. The specialized pipeline justifies some breadth, but the count is borderline excessive.
The analysis lifecycle is well covered: detection, auditing, ranking, planning, placement, stats, findings, and target explanation. However, actual test generation is explicitly deferred/non-functional and there is no write or execution surface, which is a notable gap for a test architect.