Skip to main content
Glama

owa_present_bible

Put a Bible passage on the projector by reference and confirm what is on screen. Resolve and quote a verse without displaying it when checking first.

Instructions

Put a Bible passage on the projector by its REFERENCE -- "John 3:16", "Psalm 23:1-6" -- and answer with what is on the screen now. Use it whenever the user asks for a verse to go UP: never the Bible Lookup popup and never a guide for that -- the lookup is a picker no step can drive. Without version, the version the lookup is on, then any installed one that reads the reference. action: "check" only resolves and quotes it, touching no screen. The answer is read BACK off the screens: isPresented, the passage, its first words, each ticked screen with isShowing -- an off screen holds the verse unseen until its show button is pressed, which is offered, never done unasked. Presenting changes what the congregation sees: do it when they asked for it to go up, offer it when they only asked how. Clear Bible takes it off again.

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": {
      "reference": "<reference>"
    },
    "name": "owa_present_bible"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNopresent (default) or check
versionNoAn installed Bible version key, such as KJV
referenceYesThe passage, as the user said it: book, chapter and verse or verse range.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.15

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full load and delivers: version fallback order, that action 'check' touches no screen, that results are read back off the screens including isPresented and per-screen isShowing, and that an off screen holds the verse unseen until its show button is pressed. It also flags the visible-congregation consequence of presenting.

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?

Purpose and the primary routing warning are front-loaded, and nearly every clause carries information. Some sentences are dense and clause-stacked (the 'answer is read BACK off the screens' passage), which slightly slows parsing.

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

Completeness5/5

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

No output schema exists, and the description compensates by naming the returned fields (isPresented, the passage, its first words, each screen's isShowing) along with the on/off-screen distinction. Everything needed to call or interpret it is present.

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 coverage is 100%, so the baseline is 3; the description still adds real meaning beyond the schema by explaining the fallback sequence when 'version' is omitted and that action 'check' resolves and quotes without touching a screen.

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 a concrete verb+resource: put a Bible passage on the projector by reference, and returns what is on screen now. It explicitly separates itself from the Bible Lookup popup and the guide, so an agent can pick it over siblings without opening a schema.

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?

Gives explicit when-to-use ('whenever the user asks for a verse to go UP'), explicit when-not ('never the Bible Lookup popup and never a guide for that'), a consent rule ('do it when they asked for it to go up, offer it when they only asked how'), and names where removal lives (Clear Bible takes it off again).

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