Skip to main content
Glama

owa_bible_suggest

Suggests Bible book, chapter, verse, people, and place completions for the app's chat input as a user types, and lists installed Bible book names for reference lookup.

Instructions

The chat box's input aid, read by the WINDOW as a person types -- not by you. kind "reference" completes a book, chapter and verse in the Bible being read (prefix, and book when only digits were typed); "name" suggests people and places of the names lookup; "books" lists every installed Bible's book names, which the window finds the references a study cites by. Reads only; answer with owa_find_verse or owa_lookup_record.

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": {
      "kind": "<kind>",
      "prefix": "<prefix>"
    },
    "name": "owa_bible_suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNo
kindYes
pageNo
limitNo
prefixYes
allowLoadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden, and it does add real value: it declares read-only behavior ("Reads only"), explains that the window—not the agent—is the caller, and describes what each kind enumerates. However, it says nothing about pagination, whether results are ordered, or what allowLoad does (loading a Bible module is implied by the name only), which are meaningful behavioral gaps for a 6-parameter 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?

The most decision-relevant fact (this tool is for the window, not the agent) is front-loaded in the opening clause, and the three kind modes are packed into one dense but readable paragraph. A few phrasings are clunky ("which the window finds the references a study cites by"), but nothing is redundant.

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 6-parameter tool with no annotations and no output schema, the description does the essential job of telling an agent to avoid it and pointing to the correct siblings, and it covers the enum that drives behavior. It leaves enough unexplained (page/limit/allowLoad, result shape, what allowLoad triggers) that an agent forced to actually call it would be guessing.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate and only partially does. It explains `kind`'s three enum values and clarifies that `prefix` is the typed text and `book` is used when only digits were typed; but `page`, `limit`, and `allowLoad` receive no explanation at all, leaving half the parameters undocumented anywhere.

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 states a concrete resource (the chat box input aid / Bible reference completion) and breaks the tool into three distinct modes with what each one produces: "reference" completes book/chapter/verse, "name" suggests people and places, "books" lists installed Bible book names. It also differentiates from siblings by naming owa_find_verse and owa_lookup_record as the alternatives. It falls short of 5 because the actual shape of a 'suggestion' result is never described, so an agent cannot picture the output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-not-to-use rule ("read by the WINDOW as a person types -- not by you") and names two concrete alternatives for the agent's real need (owa_find_verse, owa_lookup_record). The condition selecting each alternative is stated rather than left to inference.

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