Skip to main content
Glama

Watch Ui Events

watch_ui_events
Read-onlyIdempotent

Monitors real-time AT-SPI2 D-Bus mutation events to await UI settlement after triggers and returns captured changes plus settle status, avoiding full accessibility tree re-queries.

Instructions

Awaits UI settlement by monitoring real-time AT-SPI2 D-Bus mutation events.

Returns captured mutations and whether the UI has settled, eliminating the need to re-query the full accessibility tree after triggers.

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

Input Schema

NameRequiredDescriptionDefault
pidNo
timeout_msNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's real contribution is disclosing that this is a blocking wait on live D-Bus events and that it returns both captured mutations and a settlement verdict. The blocking nature is the key behavioral fact an agent needs and it is stated. It omits that settlement is bounded by a timeout, which is a notable gap for a blocking call.

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 tight sentences, with the core mechanism front-loaded and the payoff (no full-tree re-query) second. Terminology is technical but appropriate to the domain; no filler.

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?

Because an output schema exists, the description need not detail return values, and it does say what is returned at a high level. But for a blocking, event-driven tool with two undocumented parameters and an unmentioned timeout, an agent still lacks enough to invoke it confidently in edge cases.

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% for two parameters, so the description must carry the burden and it says nothing about either. The role of pid (which process's UI to watch) and especially the meaning/impact of timeout_ms (default a very short 500ms) are left entirely unexplained, which risks premature or hanging calls.

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 action and mechanism: block until UI settlement by watching AT-SPI2 D-Bus mutation events, returning mutations plus a settled flag. It implicitly distinguishes itself from tree re-querying ('eliminating the need to re-query the full accessibility tree'), which points at inspect_ui_tree, though no sibling is named explicitly.

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?

The phrase 'after triggers' implies the intended moment of use, and it contrasts itself with re-querying the accessibility tree. However, there is no explicit when-to-use/when-not guidance, no named alternative (e.g. inspect_ui_tree), and no advice on what to do if settlement never occurs.

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