Skip to main content
Glama

owa_foreground_edit

Modify a foreground component's saved session—words, timer, and look—then show or hide it on chosen screens. Read current settings first; changes are backed up for undo.

Instructions

Change a foreground component through its own panel: a SESSION of it (a saved set-up: its words and its look). session: the one attached or named, else the panel's current one. read first: its words, look in words, which screens hold it and every screen (open: true lists the open panels and their sessions). start puts NEW words or a time up -- in a session of its own, never over one they typed -- on the ticked screens, a countdown or stopwatch running. set changes the session -- its words (text | texts | ref, minutes | at, seconds, delay, interval, utcOffset | title | is24Hour, sound | volume, preset) and/or look {size ("larger"|"smaller"|px), color, background, blur, font, bold, position ("top", "bottom left"...), width %, scale, opacity, round, border, borderWidth, borderColor, shadow, textAlign, italic, underline, uppercase, padding, behind, onTop, blend, transition, speed} -- and what of it is on a screen changes at once. show puts the session up as it is, hide takes it off (widget all: every extra off every screen), timer start|pause|resume|reset a countdown or stopwatch on the wall, or add minutes/seconds MORE to a countdown that is up, session makes a new one (name). Leave screens out unless they named one: the ticked ones are their choice. A verse is ref, read from the installed Bible -- never write its words yourself. A field the component lacks is refused with what it takes. Every change keeps a backup owa_undo puts back. Do only what was asked; going UP changes what the congregation sees.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "owa_foreground_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
refNo
fileNo
lookNoThe look in words; read the description for every field.
nameNo
openNo
textNo
delayNo
soundNo
textsNo
timerNo
titleNo
actionYes
cameraNo
presetNo
sourceNo
volumeNo
widgetNo
minutesNo
screensNo
secondsNo
sessionNo
versionNo
intervalNo
is24HourNo
autoStartNo
utcOffsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A3.7/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 reversibility ('Every change keeps a backup owa_undo puts back'), validation behavior ('A field the component lacks is refused with what it takes'), non-destructive defaulting for `start` ('NEW words... never over one they typed'), and the live-audience side effect of changes taking effect 'at once'. It omits auth/rate-limit style operational context but covers the mutation semantics an agent needs.

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 content is dense and mostly earns its place (the `look` field list is information the schema does not carry), but it is delivered as a run-on chain of backticked clauses and nested parentheses with no paragraph or list structure. A reader must re-parse sentences like the `set` clause to extract which parameters belong to which action.

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?

For a 27-parameter mutation tool with no annotations and no output schema, the description covers actions, safety/reversibility, screen scope, and the main parameter families. It still leaves roughly a third of the parameters undocumented and does not describe what a `read` call returns beyond 'its words, look in words, which screens hold it'.

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 4% across 27 params, so the description must compensate, and it does explain the higher-value ones: the seven actions, `session`, `screens`, `open`, `widget: all`, `timer` verbs, `minutes`/`seconds`/`delay`/`interval`/`utcOffset`, `title`/`is24Hour`, `sound`/`volume`, and a long enumeration of `look` fields. Many parameters remain unexplained (file, camera, source, version, autoStart, preset values, `at` format), so compensation is partial rather than complete.

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 with a concrete verb and resource ('Change a foreground component through its own panel') and defines the unit of work as a SESSION (a saved set-up of words and look). It does not, however, position itself against siblings like owa_foreground or owa_lyric_edit, so an agent must infer the boundary from the panel framing alone.

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?

Clear situational guidance: 'read first', 'Leave `screens` out unless they named one: the ticked ones are their choice', and 'Do only what was asked; going UP changes what the congregation sees'. It also supplies a hard rule for verse content ('A verse is `ref`... never write its words yourself'). It stops short of naming an alternative tool or an explicit when-not-to-use case.

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