Bible by Midvash

get_verse

Read-onlyIdempotent

Fetches one exact Bible verse or a contiguous verse range from a specific version. Use this when the book, chapter, verse, and version are already known. For natural references such as "John 3:16-18", prefer get_passage.

Input Schema

TableJSON Schema

Name	Required	Description
`book`	Yes	Bible book name, slug, or abbreviation. Accepts supported localized names such as "John", "João", "Salmos", or "1 Sm".
`verse`	Yes	Starting verse number. Must exist in the selected chapter.
`chapter`	Yes	Chapter number within the selected book. Must be 1 or greater.
`version`	Yes	Bible version slug to read from, such as "onbv", "kjv", "bsb", or "rvr1909". Must be enabled by the connection URL filters.
`verse_end`	No	Optional ending verse number for a range. Must be greater than or equal to verse and within the same chapter.

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.

Changed3 schema fields changedOct 1, 2026

changedInput schema / properties / version / description

Previous value: -"Bible version slug to read from, such as \"nvi\", \"kjv\", \"ara\", or \"rvr1909\". Must be enabled by the connection URL filters."New value: +"Bible version slug to read from, such as \"onbv\", \"kjv\", \"bsb\", or \"rvr1909\". Must be enabled by the connection URL filters."

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

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / version / description

Previous value: -"Bible version slug to read from, such as \"nvi\", \"kjv\", \"ara\", or \"rvr1960\". Must be enabled by the connection URL filters."New value: +"Bible version slug to read from, such as \"nvi\", \"kjv\", \"ara\", or \"rvr1909\". Must be enabled by the connection URL filters."

addedOutput schema / properties / reader_url

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

First observedSep 12, 2026

TDQS

A4.3/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 without the description. The description adds the range-versus-natural-reference behavioral distinction, but says nothing about error behavior for invalid verses or version-enablement failures.

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 tight sentences with zero waste, front-loading the primary capability and then the sibling routing rule. Every sentence 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?

An output schema exists, so return-value shape need not be restated. With 100% schema coverage and full annotation coverage, the only open question for an agent, which tool to pick, is answered explicitly.

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% and every parameter, including the optional verse_end range bound, is documented in the schema itself. The description only echoes the range concept and adds no syntax or format detail beyond what the schema provides, so 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 ('Fetches'), a precise resource ('one exact Bible verse or a contiguous verse range'), and scope ('from a specific version'). It is immediately distinguishable from get_passage and get_chapter.

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 an explicit precondition ('when the book, chapter, verse, and version are already known') and names the alternative with the selecting condition ('For natural references such as "John 3:16-18", prefer get_passage'). No inference required.

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.