Bible by Midvash

get_cross_references

Read-onlyIdempotent

Finds other Bible passages that relate to a given verse, ranked by how widely the link is attested. This answers "what else in Scripture speaks to this?" — the standard next step in study after reading a verse. Returns each related passage with its text, so no follow-up lookup is needed.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of related passages. Default: 10; max: 25.
`version`	No	Optional Bible version slug for the text of the related passages. Defaults to the connection version, or "bsb" (English).
`reference`	Yes	The verse to start from, such as "John 3:16" or "Romanos 8:28". Must point at a single verse; a whole chapter is too broad for cross-references.
`include_text`	No	Whether to include the text of each related passage. Default true. Set false for a compact list of references only.

Output Schema

TableJSON Schema

Name	Required	Description
`source`	Yes
`version`	No	Version slug, such as "kjv".
`passages`	Yes
`copyright`	No	Attribution the version license requires (e.g. CC BY-SA). Present only for versions that need it; show it with the text.
`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 for the text of the related passages. Defaults to the connection version, or \"onbv\"."New value: +"Optional Bible version slug for the text of the related passages. Defaults to the connection version, or \"bsb\" (English)."

Changed3 schema fields changedOct 1, 2026

changedInput schema / properties / version / description

Previous value: -"Optional Bible version slug for the text of the related passages. Defaults to the connection version, or \"nvi\"."New value: +"Optional Bible version slug for the text of the related passages. Defaults to the connection version, 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\"."

First observedSep 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety burden is lifted. The description adds useful non-obvious context: results are ranked by attestation and include text, reducing a follow-up lookup. It doesn't mention result count limits or pagination, but the schema's limit param covers that.

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 front-loaded sentences: action, use-case framing, and return shape. No filler, and the return-value summary is placed last where it's most relevant.

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 structure needn't be explained. The description covers purpose, ranking basis, and downstream utility. Combined with full schema coverage and annotations, an agent has all it needs to invoke correctly.

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 every parameter is already documented in the schema, including the single-verse constraint and the include_text toggle. The description only broadly mentions 'given verse' and 'each related passage with its text'—no substantive additions beyond structured data. 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?

Starts with a specific verb+resource ('Finds other Bible passages that relate to a given verse') and names the ranking criterion (how widely attested). This clearly distinguishes it from siblings like get_verse, get_passage, and search_bible, which do not return ranked cross-reference lists.

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 standard next step in study after reading a verse" gives a clear usage context, implicitly contrasting with get_verse/read-first workflows. It doesn't explicitly name alternatives or when NOT to use it, but the framing is strong enough to guide selection.

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.