Skip to main content
Glama

owa_presenting_flow

Manage Open Worship presenting flows: list, create, rename, delete sheets; add, move, duplicate, park, or remove service lines. Changes are backed up for undo.

Instructions

The user's run sheets (presenting flows): the order of a service. list names them; info reads one's lines (number, title, kind, isParked); create, rename (to newName) and delete (to the trash) work on whole sheets. add puts a line into sheet name: a document (a song or slide document by its Documents-list name), a Bible reference ("John 3:16", in version), or an actionId ("clear-all", "next-timeout" with seconds, "screen-show" with screenIds; a wrong id answers with them all) -- at line at, else last. remove, duplicate, park (keep it listed, out of the run) and unpark take line; move takes line and to. Nothing reaches a screen: the operator runs the sheet. Nothing is lost: a delete goes to the trash and every change keeps a backup owa_undo puts back. Change only what was asked, then say what changed and that it can be undone.

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

Input Schema

NameRequiredDescriptionDefault
atNo
toNo
lineNoA line number from info
nameNoThe sheet as the Presenting Flows panel shows it
pageNo
actionYes
newNameNo
secondsNo
versionNo
actionIdNo
documentNo
referenceNo
screenIdsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.1/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 that deletes go to the trash, that every change keeps a backup restorable via `owa_undo`, that a wrong `actionId` returns the valid list, and that changes never reach a live screen. Missing are permission/auth requirements and error behavior for other failure modes, which for a mutation-heavy tool leaves a small gap.

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

Conciseness5/5

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

Extremely dense but every clause carries operational information (action-to-object mapping, examples, undo guarantee); nothing is filler. The structure moves from identity, to action inventory, to constraints, which is the right order for an agent scanning for a decision.

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 13-parameter, 11-action tool with no annotations and no output schema, the description covers nearly everything needed to invoke it correctly, including the shape of `info` output (number, title, kind, isParked) and the undo path. Only the undocumented `page` parameter and the absent differentiation from the sibling edit tool keep it from complete.

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 15%, so the description must compensate, and it largely does: it explains `at` ("else last"), `to`, `line`, `newName`, `document` (a Documents-list name), `reference` with `version` and a concrete example, and the `actionId` family with `seconds`/`screenIds` payloads. The `page` parameter and the `name` reuse across `add`/rename contexts are left undocumented, which is the main remaining hole.

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 identification of the resource ("run sheets (presenting flows): the order of a service") and then enumerates every action with the object it operates on, so an agent can map an intent to an action value. It stops short of contrasting itself with the sibling `owa_presenting_flow_edit`, which an agent would have to disambiguate from naming 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?

Per-action guidance is effectively explicit: `list` names sheets, `info` reads lines, `create`/`rename`/`delete` work on whole sheets, `add` inserts a document/reference/actionId, and `remove`/`duplicate`/`park`/`unpark`/`move` take line numbers. It also sets a behavioral boundary ("Nothing reaches a screen: the operator runs the sheet"). It does not name an alternative tool or state when NOT to use this one.

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