Bible by Midvash

get_passage

Read-onlyIdempotent

Fetches Bible passages from natural-language references such as "John 3:16-18", "Psalm 23", "Romans 8:1-9:5" (crossing chapters) or "John 3:16; Romans 8:1" (several at once). This is the primary lookup tool when the user gives a citation instead of structured book/chapter/verse fields.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`version`	No	Optional Bible version slug. If omitted, uses the first version enabled by the connection URL, or "bsb" (English) when no version filter exists. When the user writes in another language, pass a version in that language.
`reference`	Yes	One or more free-form Bible references. Accepts localized book names, abbreviations, whole chapters ("Psalm 23"), verse ranges ("John 3:16-18"), chapter ranges ("Genesis 1-3"), ranges that cross chapters ("Romans 8:1-9:5"), and several references separated by semicolons or commas ("John 3:16; Romans 8:1"). At most 10 per call.

Output Schema

TableJSON Schema

Name	Required	Description
`verses`	Yes
`version`	Yes	Version slug, such as "kjv".
`copyright`	No	Attribution the version license requires (e.g. CC BY-SA). Present only for versions that need it; show it with the text.
`reader_url`	No	Link to read the passage on midvash.com.
`version_name`	No	Human-readable version name.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / version / description

Previous value: -"Optional Bible version slug. If omitted, uses the first version enabled by the connection URL, or \"onbv\" when no version filter exists."New value: +"Optional Bible version slug. If omitted, uses the first version enabled by the connection URL, or \"bsb\" (English) when no version filter exists. When the user writes in another language, pass a version in that language."

Changed3 schema fields changedOct 1, 2026

changedInput schema / properties / version / description

Previous value: -"Optional Bible version slug. If omitted, uses the first version enabled by the connection URL, or \"nvi\" when no version filter exists."New value: +"Optional Bible version slug. If omitted, uses the first version enabled by the connection URL, or \"onbv\" when no version filter exists."

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\"."

Changed1 schema field changedOct 1, 2026

addedOutput schema / properties / reader_url

Added value: +{
+  "description": "Link to read the passage on midvash.com.",
+  "type": "string"
+}

First observedSep 12, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds only the routing context; batching limits (max 10) and version fallback live in the schema, not the description.

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?

Two sentences, front-loaded with purpose, and the examples are compact illustrations rather than padding. Every clause earns its place by showing reference shapes an agent must handle.

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 an output schema present, return values need no explanation, and both parameters are documented in the schema. The only thin spot is not naming the sibling tools it supersedes, but for a simple two-parameter lookup the definition is essentially complete.

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 both parameters are already fully documented in the schema, including the version fallback and the '10 per call' cap. The description restates accepted reference formats already covered, adding no syntax beyond the schema. Baseline 3 applies.

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 (fetches Bible passages) plus the exact input form it accepts (natural-language references), with concrete examples. The closing sentence distinguishes it from sibling lookup tools like get_verse/get_chapter that take structured book/chapter/verse fields.

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?

Gives a clear routing rule: use this as the primary lookup when the user supplies a citation rather than structured fields. It does not name get_verse or get_chapter explicitly as the alternatives, so the exclusion is implied rather than stated.

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 tools Inspect

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.