Skip to main content
Glama

owa_bible_item

Manage saved Bible passages and their lists: list, add, update, or delete passages; create, rename, or delete lists. Changes are backed up for undo.

Instructions

The user's saved Bible passages (the Bibles list; the Reader keeps its own). list shows the lists and each passage's id; add saves reference ("John 3:16") to list (default "Default"), in version or the Bible Lookup's; update changes passage id's reference or version; delete removes it; create-list, rename-list (to newName) and delete-list (to the trash) work on whole lists. Saving shows nothing on a screen -- that is owa_present_bible. 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_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoA passage id from list
listNoA list name as the Bibles panel shows it
pageNo
actionYes
newNameNo
versionNo
referenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful behavior: deletes go to the trash, every change keeps a backup that owa_undo restores, and saving is silent (no visual output). It never addresses error behavior, permission/auth needs, ordering or size of list results, or what a mutation returns, which leaves real gaps for a 7-parameter mutation tool.

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?

Front-loaded with the resource, then a compact per-action map, then behavioral notes -- no filler sentences. The per-action clauses are dense but each carries distinct information; the closing instruction sentence is slightly advisory but still directs correct agent behavior.

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?

With no output schema and no annotations, the description does the necessary work: it explains what list returns (the lists and each passage's id) and that writes produce no on-screen result, plus the undo/trash safety story. What mutations return and how errors surface remain unspecified, so it is strong but not airtight.

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 only 29%, so the description must compensate, and it mostly does: it documents reference syntax with an example ('John 3:16'), the list default of 'Default', the version fallback to the Bible Lookup's version, that id comes from list, and that newName is the rename target. Only page is left completely unexplained, which keeps this from 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?

States the resource (the user's saved Bible passages) and enumerates each verb the single tool performs: list, add, update, delete, create-list, rename-list, delete-list. It also distinguishes the resource from nearby ones: 'the Reader keeps its own' and the presentation sibling. An agent can map any intended operation onto an action without opening the schema.

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?

Names the alternative for the adjacent task explicitly ('Saving shows nothing on a screen -- that is owa_present_bible'), and adds a procedural rule ('Change only what was asked, then say what changed and that it can be undone'). It does not state prerequisites or when-not conditions (e.g. when to look a verse up elsewhere rather than save it), so it falls short of a full 5.

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