Skip to main content
Glama

owa_lookup_record

Look up Bible people, places, or passages by name, ID, or reference, and search names or locations to find matching records with IDs for further reading.

Instructions

Read a Bible person or place from the names lookup (drawn from the KJV), or a Bible passage. kind name|location by id (from a result's lists) or name: who or what it is, family, places, links, every verse key and the first verses quoted. Give search with kind name|location to FIND people or places by words (a partial or differently spelled name) -- the matches come back with their ids for a read. kind verse by ref ("GEN 2:19-21; John 3:16"): the passage in bible (default the lookup's); near the chapter (or verse) before or after it instead; names also the people and places in it; related also the verses its cross references lead to, by theme (one verse: all its themes). Reads only.

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>"
    },
    "name": "owa_lookup_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
refNo
kindYes
langNoThe lookup's language code; default the one shown
nameNo
nearNo
pageNo
bibleNo
namesNo
searchNoWords to find a person (name) or place (location) by
relatedNo

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, the description carries the full burden; it does disclose 'Reads only' and describes the return contents (family, places, links, every verse key, first verses quoted). However it says nothing about pagination behavior despite a `page` parameter, nor about result limits or what happens when a `ref` or `search` yields nothing.

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?

There is almost no waste — two sentences, front-loaded with the core purpose — but the second sentence is a long run-on of backticked terms and semicolons that is harder to parse than a short bulleted breakdown would be. Dense without being well-structured.

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 an 11-parameter tool with 18% schema coverage, no annotations, and no output schema, the description covers a lot of ground and is mostly callable from the text alone. The unexplained `page` parameter and the absence of any statement about result size or empty-result behavior leave real gaps for a tool of this complexity.

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 only 18%, so the description must compensate, and it largely does: it defines `kind` values, explains `id`/`name` (from a result's lists), `search` for fuzzy spellings, gives a concrete `ref` syntax ('GEN 2:19-21; John 3:16'), and clarifies `bible` default, `near`, `names`, and `related`. The `page` parameter is left entirely unexplained, which is the main gap across 11 parameters.

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 sentence gives a specific verb and resource ('Read a Bible person or place ... or a Bible passage') and names the data source (the KJV names lookup). It clearly separates the three read modes via `kind`, though it does not contrast itself with any sibling tool (e.g. owa_find_verse), leaving the agent to infer boundaries.

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?

Strong internal routing: 'Give `search` ... to FIND people or places' tells the agent to search first and then read by id, and `near`/`names`/`related` are each given a use condition. It stops short of when-not-to-use or pointing to an alternative tool for overlapping jobs.

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