VibeGuard
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| healthA | 报告 MCP 壳、状态仓库、配置与下游工具的健康状态:工具列表、状态目录、状态文件、凭据配置与过期情况,以及编排器看到的下游工具健康(在线 / 降级 / 离线 / 未使用 + 延迟)。 |
| clarifyA | 需求澄清:把一句模糊的需求逐步收窄成结构化 Spec,写入 spec.json 供 review 当判定基准。**每次调用都会返回当前该回答的问题(currentQuestion)——丢了上下文就空调用一次,它会告诉你现在该答什么。**典型流程:带 requirement 开始 → 带着 answer 与 questionId 逐问作答 → 全部答完后自动跑质量门禁,通过则产出 spec.json;不通过返回 status:"blocked" 与 nextAction,照着重答即可。想最快拿到 Spec:{requirement, skipOptional:true} 跳过可选项,两次调用即可完成。门禁未通过但确实要产出时用 force——它只放宽「验收标准条数」这类质量规则,不放宽「描述为空 / 一条标准都没有」这类结构规则(那是空基准,比没有基准更糟)。注意:.vibeguard/spec.json 不存在时 review 会降级为「无基准」分析(全部 implicit、不告警)。 |
| reviewA | 读取 git diff、扫描引用图并对照 spec.json 判定,输出按变更单元的三分类标注(in-spec / implicit / out-of-spec)与越界的事前警告,同时原子写入 changes.json 供 test 阶段读取。未找到 spec.json 时降级为「无基准」分析(全部 implicit、不告警),并在 notices 中说明。 |
| testA | 派生测试范围并执行定向回归,写入 test-results.json。范围 = spec.json 的验收标准 ∪ changes.json 的页面级影响面(读取 .vibeguard/pages.json 声明页面入口);页面映射不完整时只扩大、不缩小(并入全部冒烟页);没有 Spec 时降级为通用冒烟测试。测试失败会沿页面证据链关联相关的 out-of-spec 变更。未配置下游 test 阶段工具时返回 status:"unavailable"(该阶段没有本地兜底),绝不伪装成通过。 |
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 4 tools
The four tools map cleanly to distinct stages: health is diagnostic, clarify produces a spec, review evaluates a diff against the spec, and test derives and runs targeted regression. There is no meaningful overlap between their purposes, and the workflow ordering is obvious.
All tool names are concise lowercase single words, which is consistent and readable. The only minor deviation is that health is a noun/state check while clarify, review, and test are action verbs.
Four tools is well-scoped for a spec-driven guard workflow: clarify, review, and test form the core pipeline, and health supports diagnostics. Each tool earns its place without obvious redundancy or missing stages.
The surface covers the full clarify → review → test lifecycle plus health, with sensible degradation behavior when no spec exists. Minor gaps remain around explicitly reading generated artifacts (spec.json, changes.json, test-results.json) or initializing/resetting configuration, though agents can likely work around these via the filesystem.