Skip to main content
Glama

owa_foreground

Start or stop projector foreground extras such as countdowns, stopwatches, marquees, quick text, messages, and media shows through their own Foreground panel, or check what each screen is showing.

Instructions

Start or stop any foreground extra on the projector -- countdown, stopwatch, clock, marquee (top/bottom), quick text, message, long text, video/image/web show, camera, another screen -- through its own Foreground panel: the words go into a session of that panel and it goes up in the session's own look. Use it whenever the user asks for one to go UP or come off ("start a 5 minute countdown", "a quick text of John 3:16"): never the Foreground tab, a form for a person. A countdown takes minutes OR at (a clock time today); a marquee, quick text or message takes text or ref (a verse, read from the installed Bible -- never write a verse's words yourself). stop takes one off (all is every extra, as F10); check only reads. The answer is read BACK off the screens: did, detail, each screen with isShowing and its foreground -- an off screen holds it unseen until its show button is pressed, which is offered, never done unasked. It changes what the congregation sees: do it when asked, offer it when they only asked how.

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

Input Schema

NameRequiredDescriptionDefault
atNoCountdown to a time: "10:30", "6:45 pm", "2026-12-25 09:00".
refNoA verse: "John 3:16".
fileNoVideo/image/web show: the file by name.
textNoThe words to show.
actionNostart (default), stop or check
cameraNoCamera show: its name.
sourceNoScreen show: the screen number to show.
widgetNo"all" only with `stop`.
minutesNoCountdown length in minutes: 5, 0.5, 90.
secondsNoHow long a quick text stays.
versionNoBible version of `ref`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.9/5.0
Behavior5/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: it discloses the side effect ('changes what the congregation sees'), the return shape read back off the screens (`did`, `detail`, `isShowing`, `foreground`), and the non-obvious rule that an off screen holds the extra unseen until its show button is pressed and that this is never done unasked. That is genuine behavior beyond anything structured.

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?

It is front-loaded with purpose and usage before parameters and return semantics, and most clauses carry information. It is dense and occasionally run-on (the widget enumeration and the Bible-verse aside are packed into the same paragraph), but for an 11-parameter tool the length is defensible and nothing is redundant.

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?

Eleven parameters, no annotations, and no output schema, so the description must cover invocation rules and returns, and it does both: parameter-to-widget pairing, action semantics, and a description of what comes back. An agent could call this correctly and interpret the response without further information.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond per-field docs by giving cross-parameter rules the schema cannot express: countdown takes `minutes` OR `at`, marquee/quick text/message take `text` or `ref`, `all` is valid only with `stop`, and `ref` must be read from the installed Bible rather than authored. This is exactly the meaning an agent needs to build a valid call.

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 specific verb pair and resource ('Start or stop any foreground extra on the projector') and then enumerates the concrete widget types it covers, so the agent knows exactly what falls inside this tool's remit. It also explicitly separates itself from 'the Foreground tab, a form for a person', which is the nearest sibling confusion.

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 an explicit trigger ('whenever the user asks for one to go UP or come off') with real example utterances, names the alternative it is not, and adds a decision rule for ambiguous cases ('do it when asked, offer it when they only asked how'). The stop/check distinction is also spelled out.

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