Bible by Midvash

get_chapter

Read-onlyIdempotent

Fetches a full Bible chapter from a specific version, formatted in Markdown with numbered verses. Use this when the user needs chapter-level context instead of an isolated verse.

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

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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive semantics, so the safety profile is covered without description help. The description adds genuine behavioral context by disclosing the return format (Markdown, numbered verses), which is the useful extra here.

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 with zero filler: the primary action with its output format first, then the usage condition. Nothing repeats the name or wastes space.

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?

An output schema exists, so return values need not be re-explained, and rich annotations cover safety. Combined with 100% parameter coverage, the description is nearly complete; the only missing piece is disambiguation from the get_passage sibling.

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 three parameters (version, book, chapter) are already documented with examples and constraints in the schema. The description only gestures at 'a specific version' and adds no syntax or format meaning beyond that, so the baseline 3 applies.

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?

Names a specific verb and resource ('Fetches a full Bible chapter from a specific version') and specifies the output format, which is more than the title alone. It differentiates against an isolated verse (implying get_verse), but never addresses the sibling get_passage, so an agent cannot fully disambiguate those two from the text alone.

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?

Contains an explicit when-to-use clause ('Use this when the user needs chapter-level context instead of an isolated verse') that pairs the tool with the condition selecting it. It stops short of naming the concrete alternative tools (get_verse, get_passage) to route to.

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.