Skip to main content
Glama

owa_pick_element

Prompts the user to point at an unnamed control, captures the clicked element’s words, panel, visibility, and selector without triggering the app, and blocks until they pick or press Escape.

Instructions

Ask the user to POINT at a control: an outline follows their mouse and the next thing they click is answered with -- its words, the panel it is in, whether it is on screen, and a selector for it. Their click is swallowed, so the app does not act on it. Blocks until they pick or press Escape. Only for a control they cannot name; owa_list_ui is the answer when the words would do, and does not interrupt them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "owa_pick_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
timeoutSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.4/5.0
Behavior5/5

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

Annotations supply only openWorldHint=true, so the description carries the behavioral burden and does so thoroughly: it discloses that a modal outline appears, that the user's click is swallowed and the app does not act on it, that the call blocks until pick or Escape, and what information is returned. That is exactly the side-effect and blocking detail an agent needs before invoking a tool that hijacks the next 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?

Front-loaded with the action and the mechanism, then the guidance, then the exclusion — good ordering with no filler sentences. It is dense and slightly ornate in the enumeration ('its words, the panel it is in, whether it is on screen, and a selector for it'), but every clause carries information.

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-optional-parameter tool with no output schema, the description covers the interaction, the blocking semantics, the swallowed click, and the shape of the returned answer, which is what an agent most needs. The missing piece is failure/timeout behavior and the meanings of `page` and `timeoutSeconds`, which leaves a real gap on the control surface.

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

Parameters2/5

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

Schema description coverage is 0% and neither of the two parameters is mentioned: `page` (which page to point into) and `timeoutSeconds` (5–120) are left entirely unexplained. Worse, 'Blocks until they pick or press Escape' implies no timeout exists, which is misleading given a bounded timeoutSeconds parameter — the agent has no way to know the blocking behavior can be capped or what happens when it expires.

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 ('Ask the user to POINT at a control') and immediately characterizes the mechanism: an outline follows the mouse, the next click is captured, and the answer is the control's words, panel, on-screen state, and selector. It explicitly contrasts itself with `owa_list_ui`, so the agent can distinguish the two without opening either 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 use condition ('Only for a control they cannot name') and names the alternative with the reason to prefer it ('`owa_list_ui` is the answer when the words would do, and does not interrupt them'). This is textbook when/when-not/alternative guidance.

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