Skip to main content
Glama

owa_list_ui

Lists every visible control in a window with its on-screen label, panel, and state so you can write accurate guide steps or act on exact words instead of guessing.

Instructions

List the controls actually on screen in a window right now -- every visible button, link, box and dropdown with the words written on it, the panel it is in and where. A row says only what is unusual: isDisabled when it is greyed out, showsOnHover when the app paints it under the mouse alone; a row with neither is an ordinary enabled control. Use it BEFORE writing guide steps or acting on a control whose label you cannot guess (the Bible version button reads "KJV", not "version"), so every find is the exact words on a control that exists instead of a guess. When you name a showsOnHover control, say the mouse has to be over that part of the window first.

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_list_ui"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPart of the window URL, e.g. "reader.html"; default the main window.
limitNo
filterNoOnly controls whose label contains this text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description does heavy lifting: it defines the row contents (label text, panel, position) and the sparse-row encoding convention (isDisabled, showsOnHover; neither = ordinary enabled control), plus the hover precondition for naming hover-only controls. It omits practical traits such as result-size limits, ordering, or behavior when the page is not loaded.

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?

Well front-loaded: purpose first, then row semantics, then usage. Every sentence carries information, though the dense em-dash phrasing and parenthetical example make it slightly heavier than needed for a three-parameter list tool.

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?

No output schema exists, yet the description compensates by explaining the shape of returned rows and which optional fields appear. No annotations mean the description alone must cover behavior, and it largely does for the read-only listing use case; limits/pagination remain unexplained.

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 67% with descriptions for `page` and `filter` but none for `limit`. The description never mentions any of the three parameters, so it adds no meaning beyond the schema; 'the words written on it' only loosely gestures at the filter concept.

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 with explicit scope: 'List the controls actually on screen in a window right now' and enumerates what counts (visible buttons, links, boxes, dropdowns). The snapshot framing ('right now', 'actually on screen') distinguishes it from a targeted lookup like owa_find_ui.

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?

Gives a concrete trigger: 'Use it BEFORE writing guide steps or acting on a control whose label you cannot guess', with a vivid example (the KJV button). It also implies the downstream relation to `find` by promising exact on-screen words. It stops short of an explicit when-not-to-use statement or naming owa_find_ui as the alternative for known labels.

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