Skip to main content
Glama
WayneLiu519888

Test Impact Analysis MCP Server

repo_clone

Clones repository code to enable test impact analysis by monitoring code changes. Supports full branch initialization or incremental merge request updates.

Instructions

克隆监控仓库的代码到本地。可用于初始化(首次拉取分支代码)或更新全量代码,也可增量拉取 MR。

定位方式(二选一):

  • name = 克隆单个仓库

  • module = 克隆该模块下的所有仓库(按 repoType 各自归位)

克隆模式(通过 mode 参数控制):

  • mode=full — 全量克隆分支代码(初始化 / 强制覆盖更新)

  • mode=incremental — 增量克隆 MR:sinceDate 拉取日期后合入的 MR / sinceMrId 拉取指定 MR 后合入的 MR

存储路径(由 repoType 决定):

  • frontend → Repository/Frontend repository/{repo-name}/

  • backend → Repository/Backend repository/{repo-name}/

行为模式(自动判断,无需用户干预):

  • stdio transport → 本地模式:MCP Server 直接执行 git clone

  • http transport → 远程模式:返回结构化 git 指令,由客户端在自己本地执行 远程模式下可通过 clientBaseDir 指定客户端本地存储路径

增量模式前提:

  • 仓库必须配置了 repoType

  • 需要平台支持 MR 查询(GitHub / Generic 需 mrApiTemplate)

  • local 平台仅支持 sinceDate 模式

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo仓库别名(与 module 二选一)
moduleNo模块名(与 name 二选一)
modeYes克隆模式:full(全量)/ incremental(增量 MR)
sinceDateNoISO 日期(如 2026-06-13)。incremental 模式下拉取该日期后合入的 MR
sinceMrIdNo基线 MR/PR ID。incremental 模式下拉取该 MR 后合入的所有 MR(不含自身)
forceNo强制覆盖已存在的目录(默认 false)
clientBaseDirNo客户端代码存储根目录(仅 http transport 有效)。
Behavior5/5

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

No annotations provided, so description fully bears the burden. It discloses storage paths by repoType, automatic transport-mode behavior (stdio vs http), force override, and remote-mode return behavior. Prerequisites for incremental mode are also detailed.

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?

Well-structured with sections and bullet points, front-loading the core purpose. While lengthy, the complexity of the tool justifies the length. No redundant sentences.

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?

Given 7 parameters, 1 required, no output schema, and moderate complexity, the description thoroughly covers all aspects: positioning, modes, storage, transport behavior, and prerequisites. Agent can confidently invoke without ambiguity.

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

Parameters4/5

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

Input schema has 100% description coverage, so baseline is 3. The description adds significant semantic context: clarifies the relationship between name/module, elaborates on mode effects, explains sinceDate/sinceMrId, and provides transport-specific clientBaseDir meaning.

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?

The description clearly states it clones monitoring repository code, specifying two positioning methods (name/module) and two cloning modes (full/incremental). It distinguishes from sibling tools like impact_analysis or repo_monitor, which serve different purposes.

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

Usage Guidelines4/5

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

Provides explicit guidance on when to use full vs incremental cloning, and how to choose between name and module. Includes prerequisites for incremental mode. Lacks explicit when-not-to-use scenarios, but usage context is well-covered.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/WayneLiu519888/Test-Impact-Analysis-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server