Skip to main content
Glama

owa_app_state

Reports what the running Open Worship App is showing and where the user is: open windows, current page, selected document and slides, projector item, and run-sheet position.

Instructions

What the running app is doing right now: every live instance, its open windows, and one window's page, language, theme and visible tabs. On the Presenter page also selectedDocument -- what the user is in the MIDDLE of: the song or document they picked, its slides in order (number, name, first words), onScreen (the one of them on a screen), next and previous as the arrow keys would take them. Every slide carries find, the exact words on its card: owa_click with that PRESENTS the slide (it changes the projector -- only when asked), then owa_list_screens says what went up. And runSheet -- the run sheets (presenting flows) open in their run player: the lines of each in order, cursor (the line the run is on, and the slide inside it) and next (what the next press puts up, worked out as the Space key of the player does), or the sheets there are to open when none is. No tool advances a run: the operator presses Space in the run player, so say what is next and stop. Use it to answer in terms of what the user is actually looking at, and to check WHERE they are before telling them to go somewhere they are already standing.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPart of the window URL, e.g. "reader.html"; default the main window.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses rich reading behavior: what fields are on the Presenter page, that slides carry `find` words that map to owa_click, that owa_click changes the projector 'only when asked', and that no tool advances a run — the operator must press Space. This is substantial beyond-annotation context. It stops short of stating whether the snapshot is live/expensive or whether it triggers side effects, but the read-only nature is strongly implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose but is long and dense, packing many sub-objects (selectedDocument, runSheet, find, cursor, next) into run-on sentences. Most sentences earn their place given the rich return shape, but the density and some redundant restatements ('the slides in order' then 'find') reduce readability. It is appropriately sized for the complexity but could be more structured.

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?

Given there is no output schema and no annotations, the description accepts the burden and describes the returned structure in detail (instances, windows, page/language/theme/tabs, selectedDocument, slides, onScreen/next/previous, runSheet with cursor/next). This is sufficient for an agent to interpret the return. It does not explain the absence of output schema boundaries or whether the state can be partial, but overall it is complete for a read-only state snapshot.

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?

The schema has 100% description coverage for the single `page` parameter, so the baseline is 3. The description does not add syntax or format detail about the `page` argument (e.g., matching behavior or defaulting beyond 'default the main window'), so it adds no meaning beyond the schema.

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?

The description opens with a specific statement of the resource: live app instances, their open windows, and one window's page/language/theme/visible tabs, plus Presenter-page state (selectedDocument, runSheet, onScreen/next/previous). It clearly distinguishes itself from siblings by explicitly referencing owa_click, owa_list_screens, and by stating 'No tool advances a run' which separates it from mutation/control tools. An agent can tell this is a read-state snapshot tool versus a control tool.

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?

It gives clear usage context: 'Use it to answer in terms of what the user is actually looking at, and to check WHERE they are before telling them to go somewhere they are already standing.' It also warns 'only when asked' for the owa_click present flow, and says 'say what is next and stop' rather than advancing. However, it does not explicitly enumerate when NOT to use this versus other read tools like owa_list_screens or owa_foreground beyond the brief mentions.

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