Skip to main content
Glama

owa_screen_edit

Read or change Open Worship screen controls and Bible text styling: turn screens on or off, lock, group, select, set transitions, displays, and versions in one call.

Instructions

The screens' own controls, as each Mini Screen card and the Bible text panel set them. action "read": per screen on/off, ticked, locked, group, stage, display, transitions, Line Sync and what it shows; the Bible text style; the displays; the installed Bibles. action "set" (taken when a field is sent), many fields in one call: style -- the Bible text on EVERY screen: size ("larger"|"smaller"|px|"default"), color, bold, italic, shadow (true|"soft"|"deep"|"hard"|false), outline (true|"thin"|"thick"|false), outlineColor, glow, glowColor, look (one of read's looks), align (left|center|right|justify), lineHeight and letterSpacing ("tighter"|"looser"|number), font, backdrop (dark|light), highlight, reset; versions {add, remove}: Bibles of the passage up, by key, title or language; lineSync (versions lined up verse by verse); transition {slide, background, foreground}: none|fade|move|zoom; display by name or id; group true (the screens named together: grouped screens show the same) | a colour | false; lock; select only|add|remove|all (what is put up goes to the ticked screens); stage; show (the screen on or off -- only when asked to turn one on or off); clear bible|slide|background|foreground|all; newScreen true ALONE adds a screen, off and unticked (the answer names its number). screens: the ones they named, else leave it out for the ticked ones. Every change keeps a backup owa_undo puts back. Do only what was asked.

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

Input Schema

NameRequiredDescriptionDefault
lockNo
showNo
clearNo
groupNo
stageNo
styleNoThe Bible text look in words; the description names each field.
actionNo
selectNo
displayNo
screensNo
lineSyncNo
versionsNo
newScreenNo
transitionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A3.9/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 substantial work: every change 'keeps a backup owa_undo puts back', a new screen arrives off and unticked with its number returned, grouped screens mirror each other, and 'select' governs which screens receive what is shown. It does not describe the shape of read output or what happens on partial failure, leaving a moderate gap.

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 read/set split is front-loaded, which is the right call, but the payload is one dense run-on block of semicolons and backticks that forces re-reading; the style enumeration alone could be grouped better. Almost every clause carries information, so the problem is packaging rather than padding.

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 14-parameter tool with nested style/versions/transition objects, no annotations and no output schema, the description covers inputs, mode selection, destructive-change recovery via owa_undo, and the special newScreen rule. What is missing is the read-mode return structure and whether 'screens' applies to reads as well as writes.

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?

Schema coverage is only 7%, so the description must compensate, and it largely does: it enumerates style sub-fields (bold, italic, shadow, outline, glow, look, align, lineHeight, letterSpacing, backdrop, highlight, reset), the versions add/remove pair, transition targets, and the select/clear/transition enums, all of which appear thinly or not at all in the schema. A few fields (lock, stage, highlight) are named without any semantics, which keeps it off a 5.

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?

The description opens by scoping the tool to 'the screens' own controls' and then splits behavior into a read mode (per-screen on/off, ticked, locked, group, stage, display, transitions, Line Sync, Bible text style) and a set mode that mutates those same fields. That is a specific verb+resource pairing an agent can act on. It never names a sibling to contrast with (e.g., owa_hide_screens or owa_list_screens), so it stops short of a 5.

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 states the dispatch rule clearly: action 'read' to inspect, action 'set' 'taken when a field is sent', with many fields batchable in one call. It adds exclusion-style guidance for edge fields ('show' only when asked to turn one on or off; 'newScreen' true ALONE adds a screen) and closes with 'Do only what was asked.' No alternative tool is named, so there is no explicit when-to-use-instead routing.

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