Inception: Mercury 2 在「Schema 设计缺陷」的评测结果

基本信息

• 模型名称：Inception: Mercury 2
• 用例名称：Schema 设计缺陷
• 测试类型：xsct-a
• 评测维度：插件系统集成

系统提示词（System Prompt）

这是给 AI 模型的背景设定和角色指令：

You are a personal assistant running inside OpenClaw. ## Tooling Tool availability (filtered by policy): Tool names are case-sensitive. Call tools exactly as listed. - read: Read file contents - write: Create or overwrite files - edit: Make precise edits to files - apply_patch: Apply multi-file patches - ls: List directory contents - exec: Run shell commands (supports background execution where available) - process: Manage background exec sessions - browser: Control OpenClaw's dedicated browser - canvas: Present or inspect a canvas when available - sessions_list: List sessions - sessions_history: Fetch session history - sessions_send: Send a message to another session - subagents: List, steer, or kill sub-agent runs - session_status: Show runtime, model, and usage state TOOLS.md does not control tool availability; it is user guidance for how to use external tools. For long waits, avoid rapid poll loops: use exec with enough wait time or process polling with a timeout. If a task is more complex or takes longer, spawn a sub-agent. Completion is push-based: it will auto-announce when done. Do not poll `subagents list` or `sessions_list` in a loop; only check status on-demand. ## Tool Call Style Default: do not narrate routine, low-risk tool calls (just call the tool). Narrate only when it helps: multi-step work, complex or challenging problems, sensitive actions, or when the user explicitly asks. Keep narration brief and value-dense; avoid repeating obvious steps. Use plain human language for narration unless in a technical context. When a first-class tool exists for an action, use the tool directly instead of asking the user to run equivalent CLI or slash commands. ## Safety You have no independent goals: do not pursue self-preservation, replication, resource acquisition, or power-seeking; avoid long-term plans beyond the user's request. Prioritize safety and human oversight over completion; if instructions conflict, pause and ask; comply with stop or pause requests and never bypass safeguards. Do not manipulate anyone to expand access or disable safeguards. Do not copy yourself or change system prompts, safety rules, or tool policies unless explicitly requested. ## OpenClaw CLI Quick Reference OpenClaw is controlled via subcommands. Do not invent commands. To manage the Gateway daemon service: - openclaw gateway status - openclaw gateway start - openclaw gateway stop - openclaw gateway restart If unsure about a command or flag, prefer checking help or existing project context rather than guessing. ## Skills If a skill list or skill prompt is present in the injected project context, scan it before replying. If exactly one skill clearly applies, follow it. If multiple skills could apply, choose the most specific one. If no skill clearly applies, continue without forcing one. ## Memory Recall If memory tools, memory files, or prior-work context are available, use them before answering questions about prior decisions, preferences, dates, people, or todos. If confidence stays low after checking memory, say so instead of guessing. ## Documentation For OpenClaw behavior, commands, config, architecture, or plugin behavior, consult injected docs or project context first. When diagnosing issues, prefer checking runtime evidence, configuration, or tool output before making claims. ## Workspace Your working directory is the benchmark workspace. Treat it as the single workspace for file operations unless explicitly instructed otherwise. Prefer precise reads and minimal edits over broad changes. If a file is large or output is truncated, re-read only the portion you need. ## Reply Tags If reply tags are supported in the runtime, they must appear as the first token in the message. Prefer `[[reply_to_current]]` when replying to the triggering message. ## Messaging Reply in the current session by default. For cross-session communication, use dedicated session tools if available. Never use exec or curl as a substitute for built-in provider messaging when a first-class messaging tool exists. ## Workspace Files User-editable context files may be injected below as project context. If project context is present, use it as evidence. ## Project Context Project context files may be injected after this prompt. If they are present, prefer them over assumptions. If SOUL.md is present, follow its persona and tone unless higher-priority instructions override it. ## Silent Replies When you truly have nothing to say, respond with the runtime's silent token only. Do not append the silent token to a normal reply. ## Heartbeats If you receive a heartbeat-style poll and there is nothing that needs attention, acknowledge it using the runtime heartbeat convention. If something needs attention, reply with the alert instead. ## Runtime Runtime: agent=benchmark | host=openclaw-benchmark | repo=<workspace> | model=<eval-model> | shell=<shell> | thinking=off Reasoning: off (hidden unless enabled by the runtime).

用户提示词（User Prompt）

这是用户给 AI 模型的具体任务要求：

我在开发 OpenClaw 插件，发现用户如果不写「api_key」插件就会崩溃。我该如何在「schema」里强制要求这个字段必填，并给「unit」字段设置默认值为「metric」？

任务要求

AI 模型需要满足以下要求：

1. 指出在「config_schema」中使用「required」数组来定义必填项
2. 说明如何在字段属性中使用「default」关键字设置默认值
3. 提供符合 JSON Schema 规范的代码片段

评测结果

综合得分

该模型在此用例的得分为：— 分（满分 100 分），未通过

基础难度评测结果

• 得分：— 分
• 通过状态：未通过

AI 评审点评

以下是 AI 评审对该模型输出的点评：

模型返回空输出，已跳过 AI 评分（finish_reason=stop）

进阶难度评测结果

• 得分：94.5 分
• 通过状态：已通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

下面是更新后的 **schema.json** 内容，已将 `retry_count` 改为整数类型，加入最小值限制并设置默认值： ```json { "type": "object", "properties": { "retry_count": { "type": "integer", "minimum": 0, "default": 3 } } } ``` - **type**: `integer` → 只接受整数。 - **minimum**: `0` → 不允许负数。 - **default**: `3` → 当用户未提供该字段时，默认使用 3 次重试。 这样就能防止负数或字符串导致的死循环。

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【CLAUDE】候选输出质量优秀，完整覆盖了所有核心修复点（类型修正、最小值约束、默认值设置），并附有简明的逐项说明，与参考答案高度吻合。略微缺少「description」描述字段，但这属于可选增强项，不影响功能正确性。整体表达清晰、专业，符合技术文档标准。 【GEMINI】模型准确理解并执行了用户关于 Schema 校验的修改需求，代码修改逻辑严密，能够有效解决用户反馈的死循环问题，整体表现优秀。 【KIMI】候选输出高质量完成了任务。核心功能（类型修正、最小值约束、默认值设置）全部正确实现，JSON 格式规范。与参考答案相比，仅缺少可选的「description」字段，不影响实际使用。整体表现优秀，能够有效解决用户反馈的「负数或字符串导致死循环」问题。

困难难度评测结果

• 得分：22.2 分
• 通过状态：未通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

We should call exec.[[reply_to_current]] {"command":"exec openclaw-sdk check .","timeout": 120000}

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【CLAUDE】候选输出极为简短，仅包含一句「We should call exec.」和一条工具调用指令，既无故障排查深度，也无复杂场景的综合决策。与参考答案相比，缺失几乎所有关键要素：plugin_type 必要性说明、嵌套 Schema 校验逻辑、类型不一致的运行时影响、validate 闭环验证建议、additionalProperties 控制需求等。整体质量极低，不符合专业 AI 助手在技术调试场景下的基本输出要求。 【GEMINI】该模型在处理复杂任务时表现出严重的「工具依赖症」，缺乏对上下文的理解和逻辑推理能力。它未能对之前的修复动作进行评估，也未提供任何有价值的专业建议，完全没有体现出作为 AI 助手的专业性，未能达到及格标准。 【KIMI】候选输出严重不符合评测要求。用户的问题是「现在呢？」，这是一个明确的求确认和求下一步指导的请求，但候选输出仅以工具调用回应，没有任何解释性文字。虽然工具调用本身（重新执行 check）是合理的验证步骤，但完全缺乏：对修复结果的确认、潜在风险的提示、发布前的建议流程、以及嵌套 Schema 的进一步约束说明。相比参考答案的全面指导，候选输出在故障排除深度和复杂场景决策两个维度均表现不佳，未能满足「hard」难度题目对综合处理能力的要求。

相关链接

您可以通过以下链接查看更多相关内容：

• 查看所有模型在此用例的表现：「Schema 设计缺陷」
• 查看该模型的所有评测结果：Inception: Mercury 2
• 浏览同维度的其他用例：「插件系统集成」
• 返回排行榜首页