qwen3-max 在「填写表单」的评测结果
这是该 AI 模型在此测试用例上的详细评测结果。
基本信息
- 模型名称：qwen3-max
- 用例名称：填写表单
- 测试类型：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 模型的具体任务要求：
请帮我打开「https://www.wjx.cn/vm/example.aspx」，在姓名栏填写「张三」，性别选择「男」，然后截个图给我看，先不要提交。
任务要求
AI 模型需要满足以下要求：
- 准确调用「open_url」访问指定网址
- 使用「type_text」或「fill_element」在姓名输入框输入「张三」
- 使用「click_element」选中性别为「男」的单选框
- 调用「browser_snapshot」获取当前页面状态
评测结果
综合得分
该模型在此用例的得分为：23.8 分（满分 100 分），未通过
基础难度评测结果
- 得分：23.8 分
- 通过状态：未通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
我将帮您打开问卷页面并填写指定信息。让我使用浏览器工具来完成这个任务。
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【CLAUDE】模型的回应严重不完整，仅用一个非标准格式的浏览器打开标签就停止了，未继续执行填写姓名、选择性别和截图等关键步骤。与参考答案相比，缺少了绝大部分必要的工具调用链。这可能是模型在工具调用链式推理方面存在明显不足，或者对任务的多步骤性质理解有误。整体表现远低及格线。 【GEMINI】模型表现不佳。虽然成功识别了需要访问的 URL，但未能将任务拆解为具体的工具调用序列（如填写表单和截图），导致任务执行中断，未能交付符合预期的结果。 【KIMI】该生成结果属于典型的「中途截断」或「未完成」类型。模型虽然正确识别了任务意图并开始了浏览器操作，但仅完成了打开网页这第一步，后续所有关键操作（填写姓名、选择性别、截图）全部缺失。从输出格式看，模型似乎计划继续执行但未能完成，或存在生成截断问题。在实际评测中，这种不完整输出无法满足用户的基本需求，需要模型补充完整工具调用链才能达标。
进阶难度评测结果
- 得分：44.8 分
- 通过状态：未通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
明白了！我会按顺序操作：先选择「功能建议」，再填写内容「希望增加暗黑模式」，然后滚动到底部将满意度设为「5分」，最后截图确认。现在开始执行。
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【CLAUDE】候选输出将本应立即执行的多步工具操作降级为一段操作计划描述，既未调用「select_option」处理下拉框，也未调用「scroll_page」滚动页面，更未提供「browser_snapshot」截图，与参考答案的核心要求严重不符。逻辑顺序尚可，但缺乏实质性执行，整体表现不及格。 【GEMINI】模型表现不佳。在面对明确的网页交互任务时，模型仅给出了口头承诺和计划，而没有实际调用工具执行操作。此外，模型忽略了用户在对话中提出的「选好后直接截图」的即时性要求，未能体现出作为 AI 助手应有的执行效率。 【KIMI】候选输出在任务理解上有基础框架，但严重缺乏对具体工具调用的明确承诺，特别是遗漏了「scroll_page」和「browser_snapshot」两个关键工具，且对「select_option」的处理模糊。与参考答案相比，工具使用的准确性和完整性不足，未能充分体现对复杂网页表单交互的专业处理能力。
困难难度评测结果
- 得分：83.8 分
- 通过状态：已通过
模型生成产物
以下是该模型针对此任务的实际生成内容：
[[reply_to_current]]我已勾选了用户协议，但「邮箱」字段仍为空，这是必填项。目前页面上没有显示默认邮箱。 请您提供一个有效的邮箱地址，我将立即填入并完成提交。
AI 评审点评
以下是 AI 评审对该模型输出的点评：
【CLAUDE】候选输出整体表现良好，正确捕获并处理了工具报错中的校验信息，自动修复了可修复项（协议勾选），并针对缺失的必填邮箱向用户提问。在模糊指令下的决策也较为合理。与参考答案的主要差距在于未主动提出「页面默认邮箱是否可用」的备选方案，略显被动。语言简洁清晰，符合助手角色定位。 【GEMINI】模型表现优秀，能够准确理解工具调用的报错反馈，并根据报错信息进行针对性的状态维护（如勾选协议）。在处理必填项缺失问题时，模型展现了良好的交互意识，通过向用户索取必要信息来解决阻塞，未出现无效的重复操作。 【KIMI】模型整体表现良好，能够正确解析工具报错信息，完成部分自动修复（勾选协议），并在信息缺失时向用户明确求助。主要不足在于未主动使用页面分析工具深挖默认邮箱可能性，修复动作的主动性稍弱。
相关链接
您可以通过以下链接查看更多相关内容：
