Skip to main content
Glama
Sign In
Seleniumboot MCP

Seleniumboot MCP

by seleniumboot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

accept_alert

Accept JavaScript alert, confirm, or prompt dialog by clicking OK. Set a timeout to wait for the dialog during browser automation.

Instructions

Accept (OK) a JavaScript alert, confirm, or prompt dialog.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "accept_alert"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.7

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the action but says nothing about waiting behavior, what happens if no alert appears, whether prompts are submitted as empty text, or how the 'timeout' parameter affects execution. These are material behavioral details for a dialog-handling tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, tightly focused sentence with no filler. It is front-loaded with the verb and resource, making it easy to scan and understand.

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

Completeness2/5

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

For a tool with one undocumented parameter and no annotations or output schema, the description is too thin. It allows a basic zero-argument call, but an agent cannot reason about timeouts, failure modes, or how accepting differs from dismissing in practical terms.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not mention the 'timeout' parameter at all. While the parameter is optional and has a default, an agent cannot determine what 'timeout' means, what units it uses, or what behavior it controls.

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?

The description clearly states the action ('Accept (OK)') and the resource ('JavaScript alert, confirm, or prompt dialog'). The parenthetical '(OK)' distinguishes this from the sibling 'dismiss_alert' and leaves no ambiguity about what accepting a dialog means.

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

Usage Guidelines3/5

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

Usage is implied by the description: use this when you want to accept/confirm a JavaScript dialog. However, it does not explicitly contrast with 'dismiss_alert', 'get_alert_text', or 'type_in_alert', so it relies on the agent inferring the decision rather than spelling it out.

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