Skip to main content
Glama

owa_note_edit

Edit a user's Bible note in Open Worship App by reading numbered blocks and applying block, text, formatting, insertion, and reorder changes in one call. Changes remain unsaved until saved.

Instructions

Change the user's Bible note attached here, in its own window as the person sees it. note: its name as attached. read gives its numbered blocks (n, kind, text), hash and fonts (the font box's); from reads on. edit makes every change in ONE call (give hash), changes: {block, text?, kind?, checked?} changes block n -- with a list kind or kind section and its words as lines it becomes a block a line; {block, remove: true} removes it; {block, after} moves it (0 = top); {after, kind, text} adds one; kind section adds many, a block a line of mark-up (# heading, - item, 1. item, > quote, ---). Added kinds include the editor's Insert menu: table (a line a row, cells between |, first row the headings), columns (between |), collapsible (a title line, then its lines), page-break, equation (KaTeX), sticky (color yellow, pink, blue, mint, lavender, peach or sage), date (today or YYYY-MM-DD), poll (the question, then a line a choice), video (YouTube link), website, media (a link or a path), drawing (a line a box, "A -> B" an arrow, a first line "layout: across" / "circle" / "center"; background fills its boxes, color its lines; one in the note takes new lines, size larger/smaller, align), example (the editor's sample note), passage (ref). The toolbar, on a block or, with words, only those words in it: size ("larger", "smaller", px 8-72), font, color and background (a colour, or "none"), styles / stylesOff (bold, italic, underline, strikethrough, code, subscript, superscript, highlight, lowercase, uppercase, capitalize), clear: true (Clear Formatting), align (left, center, right, justify, start, end, none), indent ("more", "less" or 0-10; a list item nests), a code block's language and theme, linkTo: n (Link block text, to block n or its linkToWords; linkKind direction-to …). undo / redo step the note's kept history; view with invisibleCharacters true/false is the ¶. title renames. Words: bold, italic, underline, strike, code, words; keep [^…] [@…] [#…] tokens as read; a verse token names its Bible, [^(KJV) John 3:16]; a new one is a verse the app reads from the Bible it names (else bible, else the lookup's) -- [^(KJV) Hebrews 11:1] in place of a chip moves it to the KJV; the summary says which Bible each new verse came from. A new [@Name] / [#Place] a mention from the names lookup -- never write verse words yourself. A fixed block (table, picture, passage, sticky …) is never given words, a drawing's lines aside. Changes stay UNSAVED for Save in the note window; owa_undo puts each back.

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

Input Schema

NameRequiredDescriptionDefault
idNo
fileNo
fromNo
hashNo
noteNo
pageNo
bibleNo
titleNo
actionYes
changesNo
invisibleCharactersNo

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 load and does substantial work: it discloses that all changes must be sent in one call, that `hash` is required for edit, that edits are unsaved until Save in the window, that history is retained for undo/redo, and that fixed blocks (table, picture, passage, sticky) must never be given words. It also states a hard constraint: 'never write verse words yourself.' It omits any mention of permissions/auth or rate limits, and does not describe what the edit response returns beyond the summary noting the Bible source for new verses.

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?

Every clause roughly maps to a schema feature, so little is pure waste, but the text is a single dense block of telegraphic fragments ('{block, after} moves it (0 = top); {after, kind, text} adds one') with no paragraphing or headings. The core action contract is front-loaded, but the toolbar/words/verse-token rules pile up in one run-on stretch that is hard to scan. Readable only with effort.

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 very complex tool — 11 params, a deeply nested `changes` array, no annotations, no output schema — the description is unusually thorough, covering action modes, block mutation syntax, formatting options, mark-up conventions, verse/mention tokens, and the unsaved-changes lifecycle. Gaps remain around the unmentioned top-level params (id, file, page, again) and the absence of any return-shape explanation for the edit action beyond the verse-source summary note.

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% with 11 top-level params and a large nested `changes` object, so the description must compensate, and it largely does: it explains note, from, hash, title, invisibleCharacters, and enumerates nearly every `changes` field including block, text, kind, checked, remove, after, ref, size, font, color, background, styles/stylesOff, clear, align, indent, language, theme, linkTo, linkToWords, linkKind, words. It even documents the added block kinds (table, columns, collapsible, page-break, equation, sticky, date, poll, video, website, media, drawing, example) and their text conventions. It leaves `id`, `file`, `page`, and `again` unmentioned, and never notes the 200-item cap on `changes`.

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 specific verb+resource: 'Change the user's Bible note attached here, in its own window as the person sees it,' which pins down both the object (a Bible note) and the surface (the note's own window). It also enumerates the action set (read/edit/undo/redo/view) so the agent knows this is a multi-mode note tool. It stops short of naming sibling tools like owa_undo or owa_bible_note for contrast, keeping it at 4.

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?

Gives clear mode-selection guidance inside the tool: '`read` gives its numbered blocks', '`from` reads on', '`edit` makes every change in ONE call (give `hash`)', '`undo` / `redo` step the note's kept history'. It also warns the effect is deferred: 'Changes stay UNSAVED for Save in the note window; owa_undo puts each back,' which implicitly distinguishes it from the sibling undo tool. It never explicitly frames when to choose this over owa_bible_note or owa_foreground_edit, so no exclusion guidance.

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