Skip to main content
Glama
DB-25

arc-control-mcp

Click

click

Activate page elements in Arc using CSS selectors or visible text labels. Scrolls targets into view and dispatches real pointer events, reporting match counts to resolve ambiguous text matches.

Instructions

Click an element. Accepts a CSS selector or "text=Label". Scrolls it into view and dispatches a real pointer sequence, so framework handlers fire. "text=Label" matches on visible text as a substring, with exact matches ranked first, so a short label also matches longer ones. Check the returned "matches" count, and pass exact when it is above 1. Returns urlBefore, the url as it was immediately before the click: the tab snapshot can be taken before a navigation settles, so follow with wait_for_load when the click navigates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nthNoWhich match to click when several exist, 0-based. Order is exact text matches first, then substring matches, each in DOM order.
exactNoFor "text=" selectors, require the whole trimmed text to equal the label instead of containing it. No effect on CSS selectors.
tab_idNoArc tab id from list_tabs. Omit to use this agent's current tab, falling back to whatever tab is active in Arc.
verboseNoInclude the bulky element rect and longer attribute values
selectorYesCSS selector, or "text=Some label" to match on visible text (substring, exact matches ranked first)
Install Server

TDQS

A5/5.0
Behavior5/5

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

Annotations say readOnlyHint=false, openWorldHint=true, and destructiveHint=false. The description adds meaningful context beyond that: it dispatches a real pointer sequence so framework handlers fire, scrolls the element into view, and warns that urlBefore may be captured before navigation settles, recommending wait_for_load. This is rich behavioral disclosure that complements the annotations without contradicting them.

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?

Every sentence carries essential information: selector formats, real pointer behavior, matching semantics, matches count guidance, and the urlBefore caveat. It is dense but not bloated, and the essential 'Click an element' is front-loaded, so an agent gets the core purpose immediately.

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

Completeness5/5

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

For a tool with five parameters, matching subtleties, and navigation implications, the description covers everything an agent needs to call it correctly: return fields (matches, urlBefore), how to use the returned data, and when to wait for load. The lack of an output schema is compensated by the explicit mention of return values, making it fully self-contained.

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

Parameters5/5

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

Schema coverage is 100%, but the description goes further by explaining the interaction between parameters: how 'text=' matching ranks exact over substring, how nth order follows that ranking, and how the matches count guides the use of exact. This decision-rule level of explanation is exactly the added value expected beyond raw schema types.

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 starts with 'Click an element' — a specific verb and resource — and immediately clarifies the two accepted selector formats. It differentiates the tool from siblings like fill and press_key by focusing on the click action and its pointer-sequence behavior, leaving no ambiguity about what it does.

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?

It gives concrete when-to-use guidance: check the returned 'matches' count, set exact when matches exceed 1, and follow with wait_for_load after navigation. It also explains the matching ranking and scrolling, implicitly telling the agent when to rely on this tool versus a simple query or input tool. The explicit follow-up instruction is a strong usage guideline.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DB-25/arc-control-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server