Skip to main content
Glama

owa_presenting_flow_edit

Edit a service's running order by adding, reordering, copying, parking, or removing lines and setting timings, keys, colors, screens, slides, CCs, and foreground widgets in one call.

Instructions

Change one of the user's presenting flows (a service's running order). file: the flow as attached. lines reads every line: n, title, kind, how it is armed (seconds/time/key), color, screenIds, isParked, its CCs (what rides along with it), problems -- plus actions, foregroundWidgets, documentChoices and screens; with line it also lists that document's slides. update-lines makes MANY changes in ONE call: changes [...], each naming lines by their number AS READ (never renumber). A change is {add:{document | reference (+version) | actionId (+seconds|time|key, screenIds, target for a Jump to) | foreground:{widget, ...}, color}, after} -- after a line number, 0 for the top, left out for the end -- or {line, ...} with any of: after (move it), copy, park (true/false), seconds | time ("HH:mm") | key ("Ctrl+Shift+A"), color (a name, "#RRGGBB" or "none"), screenIds ([] for none), slides [{slide, park, screenIds}], foreground {fields}, cc {add:{line | actionId (+seconds)}, slide?, screenIds?, mediaControl?} to attach a CC, or cc {index, slide?, remove | screenIds | seconds | time | clearArming | mediaControl} to change one. remove-lines takes lines [n...]. Every change is kept at once (no Save) and keeps a backup owa_undo puts back -- say so. Change only what was asked.

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": {
      "file": "<file>",
      "action": "<action>"
    },
    "name": "owa_presenting_flow_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
lineNo
pageNo
linesNo
actionYes
changesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With zero annotations the description carries the full burden, and it does disclose two important traits: changes are committed immediately (no Save step) and a backup exists that owa_undo can restore, which the description explicitly tells the agent to mention. However, it says nothing about whether the flow is currently on-air/live when edited, permission requirements, failure modes, or what happens if a change block is invalid (partial application?). For a mutation tool with no annotations those gaps are material.

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 purpose is front-loaded, but the remainder is a single dense block of backticked fragments and run-on clauses with semicolons and nested braces rather than discrete sections. Every element is arguably useful, yet the flat structure makes it hard to scan for the one detail an agent needs at call time. It is information-rich but not well organized.

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 genuinely complex tool (6 params, a 120-item nested `changes` array, three actions, no annotations, no output schema) the description covers the change grammar well but omits the return shape entirely — there is no statement of whether it returns the updated line list, the `problems` found, or nothing. The undocumented `page` parameter and the lack of any error/rollback semantics beyond the backup note leave real gaps.

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 description coverage is 0%, so the description must compensate, and it largely does: it explains `file`, `lines` (the full read-out field list), `line`, `update-lines` with `changes`/`after`/`add`/`copy`/`park`/`cc`, `remove-lines`, plus accepted formats for color ("a name, '#RRGGBB' or 'none'"), time ("HH:mm") and key ("Ctrl+Shift+A"), and the critical rule to reference lines by number AS READ. The `page` parameter is never explained, and the nested `slides`/`foreground` sub-fields are only gestured at, keeping it below 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?

Opens with a concrete verb+resource: "Change one of the user's presenting flows (a service's running order)", and the parenthetical disambiguates the domain term for an agent unfamiliar with the product. It also names the three sub-modes (lines / update-lines / remove-lines) so the agent knows the scope of the tool. It does not explicitly contrast with the sibling owa_presenting_flow (presumably the read-only counterpart), so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through the action breakdown — `update-lines` for many changes in one call, `remove-lines` for deletion, `line` for reading slides — but there is no explicit "use this instead of X when Y" guidance and no naming of the non-editing flow tool. The closing instruction "Change only what was asked" is a scoping caution rather than a when-to-use rule. An agent can infer the mode selection from the action names but must still reason about it.

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