Skip to main content
Glama

owa_bible_note

Manage Bible notes in Open Worship App: list and read notes, add, update, or delete entries, and create, rename, or trash note files while keeping changes undoable.

Instructions

The user's Bible notes. list shows the note files and each note's id; read gives note id in full; add writes a note (title, text) into file (default "Default"); update changes note id's title or text; delete removes it; create-file, rename-file (to newName) and delete-file (to the trash) work on whole files. A verse's highlights and comments are their own kind: removed or renamed whole, their words edited in the Reader. 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_bible_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoA note id from list
fileNoA note file name as the panel shows it
pageNo
textNo
titleNo
actionYes
newNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses that file deletion goes to the trash, that every change keeps a backup owa_undo can restore, and that add defaults to the "Default" file. It omits permission or prerequisite requirements and says nothing about what a call returns, but the destructive-safety profile is unusually well covered.

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?

Three dense sentences front-load the action map and then the safety semantics, with no filler. The aside about highlights and comments is slightly compressed and takes a moment to parse, but it earns its place as a routing cue.

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 seven-parameter, eight-action mutation tool with no annotations and no output schema, the description covers action routing, undo/trash safety, and default file behavior. The remaining gaps are the undocumented `page` parameter and the absence of any hint about return shape for `list` or `read`.

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 29%, yet the description compensates by tying `id`, `title`, `text`, `file`, `newName`, and the action enum to concrete operations, and it supplies the default value for `file`. Only `page` is left entirely unexplained in both schema and description, which holds it below a 5.

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?

The description names a specific resource (the user's Bible notes) and enumerates every action verb: list, read, add, update, delete, create-file, rename-file, delete-file. It also carves out a boundary, saying a verse's highlights and comments are a separate kind handled whole or edited in the Reader, so an agent can tell which category of object this tool owns.

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?

Each action is paired with what it does and which identifiers it needs, so selecting an action is straightforward, and it points to owa_undo for reverting. It does not explicitly state when to prefer a sibling such as owa_note_edit over `update`, leaving that routing to inference.

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