Skip to main content
Glama

owa_bible_xml

Check a URL for XML Bible files, import a selected draft, and manage Bible translations (names, locale, digits, updates, deletes, KJV creation) in Open Worship App.

Instructions

Bibles from XML. check a url (no link: https://github.com/Beblia/Holy-Bible-XML-Format, the language in find): a page answers its .xml files; a file a draftId and choices to pick -- keys, locales, digits, nameLists (ids), recommended. names: book lists for locale; with url, read that site. import with draftId, key, locale, digits, bookNames id; cancel. info, update (title, locale, digits, bookNames: id or {"GEN": name}), delete take key. create-kjv: the app's KJV. problem: explain plainly. 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_xml"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
urlNo
findNo
titleNo
actionYes
digitsNo
localeNo
offsetNo
draftIdNo
bookNamesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden, and it does disclose key behavior: deletes go to trash and 'every change keeps a backup owa_undo puts back', plus a network-behavior note that a check page yields .xml files. That is valuable, but it omits permission/auth requirements, what import validates, and any output expectations for most actions.

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 text is compact with no filler, but it is written in dense telegraphic fragments with backtick tokens and semicolons, making it hard to parse and not front-loaded around a single clear purpose. It is short without being well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, multi-action tool with no annotations and no output schema, the definition leaves real gaps: the 'list' action, the 'offset' parameter, and expected return shapes for check/names/import are unspecified. The undo assurance is a strength, but the overall coverage is insufficient for this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage across 10 parameters, the description must compensate, and it does map many params to actions (url, find, draftId, key, locale, digits, bookNames). But several parameters are left unexplained — 'offset' is never mentioned, 'list' has no described parameters, and the distinction between 'keys', 'locales', 'nameLists', and 'recommended' as pick-choices is only loosely sketched.

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 specific resource ('Bibles from XML') and enumerates concrete actions (check, names, import, cancel, info, update, delete, create-kjv) so an agent can identify the tool's domain. It does not explicitly differentiate itself from siblings like owa_bible_item or owa_present_bible, and the telegraphic phrasing obscures the overall purpose somewhat.

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?

It gives partial routing guidance per action, e.g. 'check a url (no link: <repo URL>, the language in find)' and 'names: book lists for locale; with url, read that site', which implies when each action applies. However, it never states when to use this tool versus related bible tools, and actions like 'list' and the 'offset' parameter receive no guidance at all.

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