Skip to main content
Glama
IGELHARINE

CDPM

by IGELHARINE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Answer permission bubble

browser_permission

List open Chrome permission bubbles or press their exact buttons to unblock pages when dialogs sit outside snapshots and page tools cannot click them.

Instructions

Lists or answers Chrome permission bubbles ("site wants to: access other apps and services on this device / show notifications / know your location…"). They are browser UI: not in snapshot/screenshot, page tools can't click them, and the page often waits until they are answered. The header warns when one is open. Without button: shows the open bubbles with their exact button names. With button: presses that button (exact name as listed, e.g. "허용", "Allow", "Block", "Allow while visiting the site"). Windows, windowed slots only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoOnly when several bubbles are open: part of the bubble title (e.g. the site host) to pick one
slotYesBrowser slot 1-30. "3", "slot 3", "browser 3" → 3. If the user gives a port like 14052, subtract 14049.
agentNoYour display name, shown to other agents. Subagents must always set it. Default "claude-68d9".
buttonNoExact button name to press, as listed in the header or by calling without button
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. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations, so the description carries the burden well: discloses that bubbles aren't in snapshot/screenshot, page tools can't click them, page often blocks, header warns when open, and platform limit (Windows, windowed slots). Does not cover return format or error behavior, hence not a 5.

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?

Front-loaded with purpose, then mode behavior and constraints. Dense but nearly all sentences earn their place; the example button names are slightly verbose but illustrate localization.

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 a no-output-schema tool, the description is nearly complete: what it does, why page tools fail, when header warns, platform limits. Return value of the list mode is only implied rather than stated.

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

Parameters3/5

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

Schema coverage is 100% and parameter descriptions are already rich (slot parsing, site filtering, button exact name). Description reinforces button semantics but adds little beyond schema baseline.

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 specific verbs (lists/answers) and a precise resource (Chrome permission bubbles), with a concrete example of bubble text. Clearly distinguishes from browser_dialog and page-level tools by explaining bubbles are browser UI.

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?

Explains both modes (without button = list, with button = press) and notes the page may wait until answered, plus header warning. Lacks explicit exclusion vs browser_dialog, but mode selection is well-defined.

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