Skip to main content
Glama

owa_find_verse

Searches installed Bibles for a half-remembered verse, story, or every verse containing given words, ranking matches and showing where passages gather.

Instructions

Find in a Bible installed here a verse the user half-remembers, a story, or every verse with a word. words: what they remember, any order -- verses holding the most of them come first, rarer words breaking ties; a book named in them ("in Psalms") is the book searched; notInBible names words this Bible never uses. For a verse remembered by what it MEANS, search the words such a verse would use, then other forms and synonyms. A result also says where its words gather: passages (where a story is told; its key opens the chapter) and byBook; next is the from of the next page. refs: verses or chapters you think fit ("Matthew 6:34; Psalm 23"), quoted from this Bible -- never quote a verse it did not return. open: a result’s key, shown in the Bible Lookup (never on a screen), only when asked. No arguments: the installed Bibles.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "owa_find_verse"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNoSearch only these books: "Psalms", "Matthew, Mark"
fromNo
openNoA key from a result, e.g. "JHN 3:16" or "GEN 7"
pageNo
refsNo
bibleNoAn installed Bible's short name; default the lookup's
wordsNo

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?

No annotations exist, so the description carries the full burden and mostly meets it: it discloses result ranking (most matched words first, rarer words breaking ties), tie-breaking, the meaning of `passages`, `byBook`, and `next`, and a real safety constraint (never quote a verse the tool did not return; `open` displays in Bible Lookup, never on a screen). Gaps remain around empty-result and error behavior, and `notInBible` is referenced without being anchored to either a parameter or a result field.

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 purpose is front-loaded in the first clause, which is good, but the body is a dense chain of backticked jargon and long run-on sentences that are hard to parse on first read. Sentences such as 'A result also says where its words gather' and the unattached `notInBible` reference cost clarity without adding proportionate value.

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 7-parameter, no-annotation, no-output-schema tool, the description covers the search modes, the result structure, and the critical quoting restriction, which is close to what an agent needs. It falls short on `page` semantics and on how `book` as a parameter relates to book names embedded in `words`, leaving a small ambiguity an agent could stumble on.

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 43%, so the description has to compensate, and it does for `words` (order-insensitive, ranked, book names recognized inline), `refs` (semicolon-separated references quoted from this Bible), and `open` (a result key). It also implicitly links `from` to `next` for paging. The `page` parameter is left entirely unexplained in both schema and description, which caps the score.

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 opening states a specific verb and resource: find a half-remembered verse, a story, or every verse containing a word, inside an installed Bible. The three search intents (words, refs, open) are each named, so an agent can tell what the tool does. It stops short of distinguishing itself from Bible-adjacent siblings such as owa_bible_suggest or owa_bible_item, so it lands at 4 rather than 5.

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 explicit mode-selection guidance: use `words` for remembered text, use `refs` when you already think you know the verses, call with no arguments to list installed Bibles, and invoke `open` only when asked. It even routes meaning-based recall through a synonym-expansion procedure. What is missing is any statement of when NOT to use this tool versus a sibling.

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