Skip to main content
Glama

click

Triggers a real mouse press on a page element using its read_page ref and reports newly appeared or removed lines to verify UI changes.

Instructions

Click an element by ref (from read_page) with a real mouse event.

Reports what changed on the page: + lines appeared (new controls get refs), - lines went away.

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": {
      "ref": "<ref>"
    },
    "name": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: this is a real side-effecting mouse event, and the response reports page diffs with + lines (new controls get refs) and - lines. It omits whether the call waits for navigation/load, how failures surface, and whether existing refs stay valid after the click.

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?

Two short sentences; the primary action and its mechanism are front-loaded, with the return-value note following. No filler, though the diff notation could be tightened slightly.

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 one-parameter, no-output-schema tool this covers the essentials: what to pass, where it comes from, and what the textual result looks like. Only failure/error behavior and post-click ref validity are missing.

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 0%, so the single `ref` parameter is undocumented in the schema; the description partially compensates by naming its source (read_page) and noting that newly appeared controls receive new refs. It still never shows the shape of a ref or what happens with a stale one, so the compensation is only partial.

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?

States a specific verb (click), the resource (an element identified by ref), and the mechanism (a real mouse event, not a synthetic dispatch). It also ties the ref to read_page, so an agent can tell this apart from type/select/scroll siblings. It stops short of explicitly naming those alternatives.

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?

"ref (from read_page)" gives an implicit prerequisite: you must have called read_page first to obtain a ref. There is no explicit when-to-use/when-not, and no mention of what to do if the element isn't found or if a sibling like type or select would be more appropriate.

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