Skip to main content
Glama

owa_list_screens

Read projector screen state to see whether any screen is showing, what each screen holds, and the exact show/hide and Clear control labels for clicking.

Instructions

What is on the projector right now. isAnyShowing says whether any screen is on at all, and screens says what each one HOLDS -- showing or not: the slide (its document, its name, its first words), the Bible passage, the background, the foreground widgets, and whether it is locked. A screen that is showing with nothing on any layer is a blank projector; one that is off but holds a slide needs only its show button. controls carries the exact words on that screen's show/hide toggle and Clear buttons (and whether each Clear has anything to clear), so press them with owa_click by those words, no search; previewCard says where the Mini Screen panel sits. Call again after a press to CHECK what changed. Off the Presenter page it answers needsPage: "presenter" and isAnyShowing only -- owa_goto_page there 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_screens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.6/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 burden and does well: it discloses the return fields, the off-page fallback (needsPage: "presenter" with only isAnyShowing), and interpretive edge cases like a showing-but-empty screen versus an off screen holding a slide. It stops short of stating read-only safety explicitly or any rate/refresh constraints, so not a 5.

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 core statement and every clause carries information (field meanings, edge cases, follow-up actions). It is dense and slightly sprawling in a single paragraph, but there is little filler to cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must explain return values, and it does so field by field, including the degraded off-page response. For a zero-parameter read tool this is complete enough to call and interpret correctly.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly spends no words on parameter syntax.

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?

Opens with a concrete statement of the resource and state it reports ('What is on the projector right now') and then enumerates exactly what the response contains (isAnyShowing, screens, controls, previewCard). An agent can distinguish this from owa_hide_screens or owa_list_ui without opening any 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 explicit when-to-use guidance: call again after a press to check what changed, press the returned control words with owa_click rather than searching, and call owa_goto_page first when off the Presenter page. It names the alternative tools and the conditions that select them.

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