Skip to main content
Glama

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

Search the text

search_text
Read-onlyIdempotent

Returns the verses that match a search of the text, in Bible order, each with its reference, link and text; 10 per page by default (limit 1-25, and nextOffset continues). English by default; language=hebrew|greek|aramaic searches the original with vowel points and accents ignored. Every word must be in the verse; "quoted phrase" matches exact order; a trailing * matches word endings (lov*); English words are matched as written, without stemming. Narrow with book, testament (tanakh|new testament|apocrypha) or edition. Use when the user searches for words or phrases in the text itself.

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": {
      "query": "<query>"
    },
    "name": "search_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNorestrict to one book, e.g. Isaiah
limitNohow many results to return (1-25, default 10)
queryYesthe words or "quoted phrase" to find; a trailing * matches word endings (lov*)
formatNooptional: json (default) or markdown (compact, readable)
offsetNohow many results to skip; the previous answer's nextOffset is where its page ended
editionNowhich text, e.g. septuagint, onkelos, pseudo-jonathan, jonathan, hebrew-nt, hebrew or greek
languageNowhich text is searched: english, hebrew, greek or aramaic
max_charsNooptional: cap the answer at about this many characters (lists are shortened and marked truncated; use offset/nextOffset to get the rest)
testamentNotanakh, new testament or apocrypha

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. Changed6 schema fields changed
    • addedInput schema / properties / book / description
      Added value: +"restrict to one book, e.g. Isaiah"
    • addedInput schema / properties / edition / description
      Added value: +"which text, e.g. septuagint, onkelos, pseudo-jonathan, jonathan, hebrew-nt, hebrew or greek"
    • addedInput schema / properties / language / description
      Added value: +"which text is searched: english, hebrew, greek or aramaic"
    • 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 / query / description
      Added value: +"the words or \"quoted phrase\" to find; a trailing * matches word endings (lov*)"
    • addedInput schema / properties / testament / description
      Added value: +"tanakh, new testament or apocrypha"
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavior: default page size of 10 with a 1-25 limit, that nextOffset continues paging, that Hebrew/Greek/Aramaic searches ignore vowel points and accents, that matching is conjunctive per word, and that English matching is literal with no stemming. It does not cover the max_chars truncation or format behavior, which live only in the schema.

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?

Front-loaded with the return contract and pagination, then search semantics, then the usage trigger — a sensible order. The main body is one long semicolon-chained sentence, which is dense but each clause carries a distinct rule; nothing is filler, though the readability cost is real.

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 9-parameter tool with no output schema, the description does the heavy lifting: it names what each result contains, the ordering, default and maximum page size, and how to continue paging. Only format and max_chars are left entirely to the schema, a minor gap given 100% schema coverage.

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 earns more by explaining interactions the schema does not, notably that language=hebrew|greek|aramaic searches the original with vowel points and accents ignored, and how the query operators compose (all words required, quoted phrase exact order, trailing * as a word-ending wildcard). It restates the wildcard rule already in the schema, and leaves format and max_chars unmentioned.

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 specific verb and resource ("Returns the verses that match a search of the text") and immediately specifies the return payload: reference, link, text, in Bible order. The clause "searches ... in the text itself" signals it is a text-string search rather than a lexicon/word-entry lookup, which tells an agent how it differs from search_words or query_words without opening other schemas.

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 closing sentence gives an explicit trigger: "Use when the user searches for words or phrases in the text itself." That is a clear context for selection. It stops short of naming an alternative and saying when NOT to use it (e.g. word-level or morphology lookups), so it is not a full routing rule.

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