Skip to main content
Glama

owa_resource_file

Locate, read, and draft study resource files—PDFs, notes, links, and images—by Bible book and chapter, then translate or edit them for the Open Worship App.

Instructions

The user's Resources files: study PDFs, notes, links and pictures named by book and chapter (LUK.6.pdf is Luke 6, LUK.0 its introduction). list by book (+ chapter) or search, or by ref (a book and chapter together: "John 3") -- a book may be named in any installed Bible's own language, its English name or its code; read a file as listed, or its bare file name when only one file in the folders has it -- a PDF returns up to eight pages as complete pictures, starting at page (default 1); nextPage says where to read on. An embedded text layer is excluded because legacy fonts can decode to unrelated characters. Omit pages for the whole PDF; set it only to deliberately narrow a read. Use detail high for dense or unclear print. A long text file returns its start and its headings; section reads one. draft a study file for ref (a passage: "Matthew 3:3-7") from a 2-6 word title and your Markdown content (## sections, ```mermaid diagrams, each verse as [^Book C:V], never quoted); the app quotes the passage, names the file and writes NOTHING -- the person presses Create under your answer. To change a study file in Default or Bible Notes, draft with file and section (a heading) + content (its new text), or append (words added at the end of it, or of section); content alone is the WHOLE new text. To fix words where they stand -- a name, a misspelling -- draft with file and replace: each from copied exactly from the file, written as its to; nothing else moves. section with remove true takes that part out, its subparts with it. translate a study file: file, language and place ("append" adds the translation after it, "replace", "new" a copy); the help window translates it part by part, diagrams kept -- elsewhere it answers the parts to translate. save and preview are the person's presses.

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

Input Schema

NameRequiredDescriptionDefault
toNo
refNoA book and chapter, e.g. "John 3"; to draft, a passage
bookNo
fileNo
hashNo
nameNo
pageNo
bibleNo
pagesNo
placeNo
titleNo
actionYes
appendNo
detailNo
removeNo
searchNo
chapterNo
contentNo
replaceNo
sectionNo
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so in detail: `draft` writes NOTHING and the person presses Create; PDFs return up to eight pages as pictures and exclude text layers; long text files return their start and headings; translation behavior differs between the help window and elsewhere. This is unusually strong disclosure of side effects and return behavior for a tool with no annotation coverage.

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 content is dense and mostly relevant, but it is delivered as one long semicolon-chained paragraph that is difficult to scan. It front-loads the resource identity but does not structure the many action modes and parameters into easily parseable sections.

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 21-parameter, six-action tool with no output schema and no annotations, the description is rich on read/draft side effects but still leaves some parameters (`hash`, `name`, `bible`, `to`) and return shapes for list/search/draft unclear. It is adequate for the core flows but not complete for the full tool surface.

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 5%, so the description must compensate, and it explains most parameters: `book`, `chapter`, `ref`, `search`, `file`, `page`, `pages`, `detail`, `section`, `content`, `title`, `append`, `replace`, `remove`, `language`, and `place`. However, it leaves `hash`, `name`, `bible`, and `to` without clear explanation, so coverage is strong but incomplete.

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 by naming the exact resource ('the user's Resources files') and enumerates the main operations: list, read, draft, translate, save, and preview. It distinguishes the resource implicitly from lyric/media/slide siblings, though it does not explicitly name or compare those alternatives.

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?

It gives clear action-level routing: `list` by `book`/`chapter`, `search`, or `ref`; `read` a listed file; `draft` for a passage; `draft`/`append` to change a study file; `replace` for in-place word fixes; `translate` for translations. It also clarifies that `save` and `preview` are the person's presses, but it does not explicitly say when not to use this tool versus a sibling tool.

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