Skip to main content
Glama
Sign In
CDPM

CDPM

by IGELHARINE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Handle dialog

browser_dialog

Accept or dismiss browser dialogs like alerts, confirms, prompts, and beforeunload to keep a tab unfrozen. Solve blocked automation by handling dialog content yourself or asking the user.

Instructions

Accepts (accept: true) or dismisses (accept: false) an open dialog (alert/confirm/prompt/beforeunload). The tab is frozen while a dialog is open. Usually judge from its content and handle it yourself (accept if it is part of the requested task; close unneeded notices/ads). Ask the user only when it confirms an irreversible action they didn't request (payment, deletion, etc.). beforeunload: accept = leave page (input lost), dismiss = stay. For prompt, text is the input.

Input Schema

NameRequiredDescriptionDefault
tabNoTarget tab: number (1, 2…) or ID ("t7"). Use the stable ID when agents share a slot. Required for action tools when there are multiple tabs.
readNoAppend the page after the action (no separate read needed): text=body text, snapshot=snapshot page 1 (with refs), changes=only lines added/removed since your last snapshot (shortest; full page if the page changed)
slotYesBrowser slot 1-30. "3", "slot 3", "browser 3" → 3. If the user gives a port like 14052, subtract 14049.
textNoText for a prompt dialog (used only when accepting)
agentNoYour display name, shown to other agents. Subagents must always set it. Default "claude-1e1b".
acceptYestrue = OK, false = cancel
summaryNoOne-line note of what you are doing (e.g. "comparing laptop prices"). Shown in browser_status (not the status line). Omit to keep the previous one.
multiSlotNotrue only when one agent must handle several slots together (e.g. comparing). Normally omit (one agent = one slot; use subagents for the rest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.10
    • changedInput schema / properties / agent / description
      Previous value: -"Your display name, shown to other agents. Subagents must always set it. Default \"claude-68d9\"."New value: +"Your display name, shown to other agents. Subagents must always set it. Default \"claude-1e1b\"."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely succeeds: it discloses that the tab is frozen while a dialog is open, that beforeunload accept loses input, and that prompt text is only used when accepting. It does not say what happens if no dialog is open (error vs no-op) or whether the call surfaces the dialog message back, which are the remaining behavioral gaps.

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?

The action and its default policy are front-loaded in the first two sentences, and the beforeunload/prompt edge cases follow. It is dense and uses nested parentheses, but every sentence carries actionable content rather than filler.

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

Completeness4/5

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

For an 8-parameter mutation tool with no annotations and no output schema, the description covers the behaviorally risky parts (frozen tab, irreversible confirmation escalation, beforeunload tradeoff) while the schema fully documents plumbing parameters like tab, slot, agent, and read. Only the no-dialog-open failure mode is left unspecified.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: accept:true/false is tied to OK/cancel semantics and to leave-page-vs-stay for beforeunload, and text is scoped to prompt dialogs when accepting. That is real semantic enrichment on top of the schema's shorter 'true = OK, false = cancel'.

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?

States a specific verb pair (accepts/dismisses) and resource (an open dialog), and enumerates the dialog types it handles (alert/confirm/prompt/beforeunload). No sibling tool touches dialogs, so an agent can uniquely identify this one from name plus description alone.

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

Usage Guidelines5/5

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

Gives explicit decision rules: judge from content and handle it yourself by default, ask the user only when the dialog confirms an irreversible action the user didn't request (payment, deletion). It also maps accept/dismiss to concrete outcomes for beforeunload, which is exactly the when-to-choose guidance an agent needs.

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

Deploy Server

Other Tools