Skip to main content
Glama

Bible by Midvash

by com.midvash
OverviewDiscussionsAdmin

search_bible

Read-onlyIdempotent

Searches the Bible text for words or an exact phrase and returns matching verses ranked by relevance. Matching ignores letter case, accents, and Hebrew and Arabic vowel marks; wrap the query in double quotes for an exact phrase. Use this for discovery questions like "find verses about love". For a known citation, use get_passage or get_verse.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bookNoOptional book name, slug, or abbreviation in any supported book locale (ex.: "John", "João", "Salmos").
limitNoMaximum number of matches to return. Default: 20; max: 50.
queryYesWords to search for. Every word must appear in the verse, in any order. Wrap the whole query in double quotes for an exact phrase. Accents and letter case are ignored. This is keyword search, not semantic search.
versionNoOptional Bible version slug such as "onbv", "kjv", "bsb", or "rvr1909". If omitted, uses the first version enabled by the connection URL, or "bsb" (English). When the user writes in another language, pass a version in that language.
testamentNoOptional testament filter. Use "old" for Old Testament or "new" for New Testament. Ignored when book is provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
matchesYes
versionYesVersion slug, such as "kjv".
strategyNoHow the results were produced: ranked on the requested version, ranked on another version of the same language, substring fallback, or a book-scoped scan.
copyrightNoAttribution the version license requires (e.g. CC BY-SA). Present only for versions that need it; show it with the text.
version_nameNoHuman-readable version name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / book / description
      Previous value: -"Optional book name, slug, or abbreviation in any supported book locale (ex.: \"John\", \"João\", \"Salmos\"). Required for versions in Hebrew, Greek, or Latin."New value: +"Optional book name, slug, or abbreviation in any supported book locale (ex.: \"John\", \"João\", \"Salmos\")."
  2. Changed1 schema field changed
    • changedInput schema / properties / version / description
      Previous value: -"Optional Bible version slug such as \"onbv\", \"kjv\", \"bsb\", or \"rvr1909\". If omitted, uses the first version enabled by the connection URL, or \"onbv\"."New value: +"Optional Bible version slug such as \"onbv\", \"kjv\", \"bsb\", or \"rvr1909\". If omitted, uses the first version enabled by the connection URL, or \"bsb\" (English). When the user writes in another language, pass a version in that language."
  3. Changed3 schema fields changed
    • changedInput schema / properties / version / description
      Previous value: -"Optional Bible version slug such as \"nvi\", \"kjv\", \"ara\", or \"rvr1909\". If omitted, uses the first version enabled by the connection URL, or \"nvi\"."New value: +"Optional Bible version slug such as \"onbv\", \"kjv\", \"bsb\", or \"rvr1909\". If omitted, uses the first version enabled by the connection URL, or \"onbv\"."
    • addedOutput schema / properties / copyright
      Added value: +{
+  "description": "Attribution the version license requires (e.g. CC BY-SA). Present only for versions that need it; show it with the text.",
+  "type": "string"
+}
    • changedOutput schema / properties / version / description
      Previous value: -"Version slug, such as \"nvi\"."New value: +"Version slug, such as \"kjv\"."
  4. Changed1 schema field changed
    • changedInput schema / properties / version / description
      Previous value: -"Optional Bible version slug such as \"nvi\", \"kjv\", \"ara\", or \"rvr1960\". If omitted, uses the first version enabled by the connection URL, or \"nvi\"."New value: +"Optional Bible version slug such as \"nvi\", \"kjv\", \"ara\", or \"rvr1909\". If omitted, uses the first version enabled by the connection URL, or \"nvi\"."
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-open-world traits, so the bar is lower. The description adds meaningful behavioral detail beyond them: case/accent/vowel-mark normalization and the double-quote exact-phrase convention that changes what matches. It does not cover pagination or result-size behavior, but the output schema exists to carry return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences with zero filler, front-loading what the tool does before the normalization rules and the sibling routing. Every clause earns its place.

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?

For a search tool with full schema coverage, an output schema, and annotations covering the safety profile, the description supplies everything an agent needs to select and invoke it correctly, including the alternative tools for the citation case.

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 parameters are already fully documented, giving a baseline of 3. The description restates the exact-phrase quoting and normalization behavior already present in the query parameter description rather than adding semantic detail beyond the schema.

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 ('Searches the Bible text for words or an exact phrase') and immediately names the resource returned ('matching verses ranked by relevance'). It distinguishes itself from siblings by contrasting with get_passage/get_verse in the same paragraph.

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 ('discovery questions like "find verses about love"') and a when-not-to-use with named alternatives ('For a known citation, use get_passage or get_verse'). Nothing is left to inference.

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

All Bible by Midvash toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources