Skip to main content
Glama

Browser Click

browser_click

Clicks a UI element by CSS selector to automate SAP GUI navigation and interactions; check keyboard shortcuts before clicking buttons for reliable execution.

Instructions

Click an element by CSS selector. BEFORE clicking buttons, use sap_get_shortcuts to check if a keyboard shortcut is available - shortcuts are faster and more reliable than clicks.

Session parameter:

  • session=None (default): Uses primary session ("s1")

  • session="s2": Targets specific session (for parallel agents)

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": "browser_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoSession ID (e.g., "s1", "s2"). None uses primary session.
agent_idNoAgent identifier for binding check. Optional.
selectorYesCSS selector of the element to click.

Output Schema

NameRequiredDescriptionDefault
errorNoError message if success=False
popupNoPresent when a popup dialog is active on screen
successNoWhether the operation succeeded
selectorYesSelector that was clicked
active_windowNoWhich window was operated on (e.g., 'wnd[0]', 'wnd[1]'). If 'wnd[1]' or higher, a modal dialog is open.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it says nothing about what happens on click: no mention of auto-waiting for element visibility, scroll-into-view, behavior when the selector matches multiple elements, or what happens when the click triggers navigation or an error. The only behavioral content is the shortcut-check recommendation, which is workflow advice rather than disclosure of how the tool behaves.

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 core action is front-loaded in the first sentence and the shortcut warning follows logically. The bolded session block partially repeats what the 100%-covered schema already states, which is mild redundancy rather than bloat.

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

Completeness3/5

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

An output schema exists and all three parameters are documented, so return values and inputs are covered. What is missing for an action tool with no annotations is click failure and waiting semantics, which an agent needs in order to invoke this reliably in automated flows.

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 selector, session, and agent_id are already documented in the schema. The description restates session semantics ('s1' default, 's2' for parallel agents) but adds nothing about selector syntax or agent_id, so it sits at the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Click an element by CSS selector'), which is unambiguous on its own. It does not distinguish itself from SAP-specific siblings such as sap_click_button or sap_click_table_cell, so an agent working inside a SAP screen still has to infer which click tool applies.

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?

It gives one explicit routing rule with a precondition: before clicking buttons, check sap_get_shortcuts because shortcuts are faster and more reliable. That is clear when-to-use advice, but it offers no guidance on choosing between browser_click and the sap_click_* siblings, which cover overlapping ground.

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