Skip to main content
Glama
Repo Test Architect

Repo Test Architect

Review Repository

review_repository
Read-onlyIdempotent

Audit an unfamiliar repository's test architecture by detecting project roots and returning a bounded, deterministic review with blockers, top findings, ranked candidates, and verification commands.

Instructions

Start here for an unfamiliar repository or a general test-architecture review. Detect and audit all project roots once, then return a bounded deterministic review: summary counts, blockers, top findings, the top-ranked candidates and plan items with execution hints, verification commands, and stats. limit caps the ranked lists (default 25) and per-test evidence is reduced to counts, so the result stays small on large monorepos. Use explain_target with repoRoot and projectRoot for one target's evidence, and analyze_repository only when the complete bundle is explicitly needed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repoRoot": "<repoRoot>"
    },
    "name": "review_repository"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum ranked candidates and plan items to return. Defaults to 25.
goTargetNo
repoRootYesRepository root path.
changedPathsNoOptional repository-relative source paths to limit target selection.
excludeProjectRootsNoOptional project roots or subtree patterns such as examples/** to exclude before the review.

Output Schema

NameRequiredDescriptionDefault
rootYes
statsYes
summaryYes
blockersYes
findingsYes
auditSummaryYes
topPlanItemsYes
schemaVersionYes
topCandidatesYes
topExecutionHintsYes
verificationCommandsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered; the description adds genuinely new behavior: single-pass detection of all project roots, deterministic and bounded output, per-test evidence collapsed to counts, and limit-driven result size for monorepos. It does not cover cost/latency on very large repos, but the size guarantees substantially reduce uncertainty.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the 'start here' cue, then scope, then result shape, then sibling routing. The middle enumeration of return contents is long and partly duplicates the output schema, but every clause still conveys scope or sizing behavior rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter tool with a nested goTarget object and an output schema, the description covers purpose, when to prefer it, result size behavior, and sibling alternatives. Return values need not be re-explained given the output schema, so nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the schema already documents repoRoot, changedPaths, excludeProjectRoots, goTarget and limit. The description only reinforces limit's effect (caps ranked lists, default 25) and adds no guidance on when to use changedPaths or excludeProjectRoots, so it adds marginal meaning beyond structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (detect and audit project roots, return a bounded review) and explicitly positions itself as the entry point versus explain_target and analyze_repository. An agent can distinguish it from the many sibling audit/rank/generate tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("Start here for an unfamiliar repository or a general test-architecture review") plus named alternatives with conditions: explain_target with repoRoot and projectRoot for one target's evidence, analyze_repository only when the complete bundle is explicitly needed. This is a full routing decision tree.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.