Skip to main content
Glama

Besorah — the Bible in Hebrew, Greek, Aramaic and English

Every verse a word is in

get_word_occurrences
Read-onlyIdempotent

Lists every verse that contains a Strong's number (Hebrew Tanakh, Greek New Testament and Septuagint), in Bible order with the verse text, plus the count per book. Covers every form of the word; optionally limited to one book. 10 verses per page by default (limit 1-25, and nextOffset continues). Use when the user asks where a particular Hebrew or Greek word occurs.

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": {
      "strongs": "<strongs>"
    },
    "name": "get_word_occurrences"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNorestrict to one book code or name, e.g. PSA or Psalms
limitNohow many results to return (1-25, default 10)
formatNooptional: json (default) or markdown (compact, readable)
offsetNohow many results to skip; the previous answer's nextOffset is where its page ended
strongsYesa Strong's number such as H2617 (Hebrew) or G26 (Greek)
max_charsNooptional: cap the answer at about this many characters (lists are shortened and marked truncated; use offset/nextOffset to get the rest)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"1-25, default 10"New value: +"how many results to return (1-25, default 10)"
  2. Changed3 schema fields changed
    • addedInput schema / properties / book / description
      Added value: +"restrict to one book code or name, e.g. PSA or Psalms"
    • addedInput schema / properties / offset / description
      Added value: +"how many results to skip; the previous answer's nextOffset is where its page ended"
    • addedInput schema / properties / strongs / description
      Added value: +"a Strong's number such as H2617 (Hebrew) or G26 (Greek)"
  3. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive lookup, so the description's main added value is pagination behavior: 10 per page by default, limit 1-25, nextOffset continues. It also discloses that all word forms are included and that results carry verse text plus per-book counts — useful context beyond annotations — but says nothing about ordering edge cases or result caps beyond max_chars.

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?

Four tightly packed sentences, front-loaded with what the tool returns and what the output contains, with usage guidance last. No filler, though the pagination clause repeats numbers already in the schema.

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?

With no output schema, the description appropriately describes the return shape (verse text, Bible order, per-book counts) and continuation semantics via nextOffset. It is largely sufficient for a read-only lookup, with only minor gaps around truncation and ordering details.

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

Parameters3/5

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

Schema description coverage is 100%, so all six parameters are already documented. The description largely restates schema facts (10 per page default, limit 1-25, optional single book) and only adds marginal nuance with 'covers every form of the word' for the strongs input.

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?

States a specific verb and resource (lists every verse containing a Strong's number) across named corpora (Hebrew Tanakh, Greek NT, Septuagint), and says what comes back (verse text in Bible order, count per book). It does not name any sibling such as get_word or search_words, so the agent must infer the boundary from 'every form of the word' versus a lexicon-word lookup.

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?

The final sentence gives an explicit use condition: 'Use when the user asks where a particular Hebrew or Greek word occurs.' That is a clear trigger, but there are no exclusions or named alternatives (e.g., when to prefer get_word for definitions or search_words for substring search).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources