Skip to main content
Glama

Request Capture Confirm Dialog

request_capture_confirm_dialog

Ask the user through a system dialog to confirm starting browser API request capture for a session. Blocks until answered; if declined, the session remains ready for another confirmation attempt.

Instructions

可选兜底:弹出系统对话框让用户点选「是/否」,是则开始记录。

confirm_login_ready 等价,只是把「问用户」交给系统对话框,供 Agent 不便在对话里询问时使用。点「否」不丢弃——会话保持等待,可再次调用 (对话框可重复弹出)。调用会阻塞到用户作答为止。会话已结束时会被拒绝。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

无注解,描述承担全部行为披露责任。明确说明阻塞行为、可重复调用、会话结束时拒绝等关键特性。这些信息超越工具名称和模式,让代理理解调用后果。虽未提及权限或返回值,但已覆盖主要行为风险。

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?

描述由三句话组成,先说明目的,再与替代工具比较,最后列出关键行为,逻辑清晰且无冗余。信息密度高,但中文表达稍显口语化,不影响理解。整体精炼,接近满分。

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

Completeness3/5

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

工具有输出模式但描述未提及返回值,且未说明错误处理(如会话结束时的具体表现)。尽管阻塞、可重复调用等核心行为已覆盖,但对于调用后如何解读结果缺乏指引。鉴于工具复杂度较低且输出模式可能存在,信息基本可用,但仍有提升空间。

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

Parameters2/5

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

schema 描述覆盖率为 0%,描述中完全未提及 session_id 参数的含义或用法。虽然参数名称自解释,但描述未提供任何额外信息帮助代理正确填充,未能补偿 schema 的缺失。仅因参数简单且唯一,给予 2 分。

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?

描述明确说明工具行为:弹出系统对话框让用户确认是否开始记录,并明确与 confirm_login_ready 等价但采用不同交互方式。动词具体(弹出、点选),资源明确(系统对话框),且与兄弟工具形成清晰区分,无歧义。

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?

描述指明适用场景为'Agent 不便在对话里询问时',并说明与 confirm_login_ready 的等价性,暗示替代选择。同时描述了点'否'后会话保持等待、可重复调用的行为,提供了明确的何时使用指引,但未明确列出何时不使用(如会话已结束时会被拒绝已隐含)。

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