Skip to main content
Glama

dev_click

Click a UI element in the Unflick window after waiting for its CSS selector; obstructed or ambiguous matches are refused, so failed clicks are not reported as success.

Instructions

Click an element in the unflick window. Polls for the selector first, so a click issued right after an action does not race the render, then hit-tests the point before dispatching: if something else is on top, the click is refused and the covering element is named rather than reported as a success. A selector matching several elements is refused unless index says which.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>"
    },
    "name": "dev_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoWhich match, 0-based, when the selector is ambiguous.
selectorYesCSS selector. Take it from dev_snapshot.
timeout_secondsNoHow long to wait for the selector to appear. Default 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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 behavioral burden and does so unusually well: it discloses the polling-before-click behavior, the pre-dispatch hit test, and the failure mode where a covering element causes a refusal instead of a false success. It does not cover what a successful click returns or whether the element is scrolled into view first.

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?

Two densely packed sentences, front-loaded with the action, then rationale, then the refusal rules. Every clause conveys a distinct behavior; nothing is redundant.

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 parameterless-annotation, no-output-schema interaction tool, the description covers the main risks (race conditions, overlapping elements, ambiguous selectors) that would otherwise cause silent failures. Only the success return value is left unstated, which is a modest gap given there is no output schema.

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 description coverage is 100%, so all three parameters are already documented, and the description's note that an ambiguous match is refused unless `index` says which largely restates the schema's own wording. `timeout_seconds` is not elaborated in the description at all, so it adds little beyond the structured fields.

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 and target ('Click an element in the unflick window') plus the exact scope of what it will and won't click (ambiguous selector refused without index). An agent can distinguish this from dev_snapshot/dev_eval/dev_wait without opening a schema.

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?

Implies the correct usage context ('a click issued right after an action') and thereby tells the agent it need not pre-call dev_wait, and it names the disambiguation requirement for multi-match selectors. It stops short of explicitly naming an alternative tool or stating when not to click.

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