Skip to main content
Glama

owa_highlight_selector

Highlights the exact element named by a CSS selector for four seconds in the live window, confirming the resolved target without guessing or matching by label.

Instructions

Ring the exact element a CSS selector names, for four seconds, in the real window. Only for a selector something already resolved -- owa_pick_element answers with one. Use owa_find_ui to find a control by its words; this one does no matching and no guessing, which is the point: it lights up the element that was meant, not another one wearing the same label.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
selectorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses the four-second duration, that it operates on the real window, and that it performs no matching or guessing (implying a purely visual, non-destructive effect). It stops short of stating failure behavior — what happens with an invalid selector or a selector that matches nothing, and whether the page scrolls into view.

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 the action and duration, then the precondition, then the sibling routing — a sensible order. The closing clause ('which is the point: it lights up the element that was meant, not another one wearing the same label') is mildly rhetorical but does reinforce the determinism guarantee.

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 two-parameter visual helper with no output schema and no annotations, the description covers purpose, precondition, and alternatives adequately. The gaps are the unmentioned `page` parameter and undefined behavior on a non-matching selector.

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 description must compensate and it does for `selector`: it clarifies that the value must be a pre-resolved CSS selector, not a label or text query, which is meaningfully more than the schema's bare type string. The `page` parameter is never mentioned, leaving an undocumented parameter against zero schema coverage.

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 resource — 'Ring the exact element a CSS selector names' — plus its scope (four seconds, real window). It explicitly distinguishes itself from both owa_pick_element (which produces a selector) and owa_find_ui (which matches by words), so an agent can identify it without opening a sibling schema.

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?

Gives an explicit precondition ('Only for a selector something already resolved'), names the tool that produces that input (owa_pick_element), and routes the matching use case to owa_find_ui. When-to-use and when-to-use-something-else are both stated.

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