Skip to main content
Glama

get_cross_references

Read-onlyIdempotent

Find the passages traditionally read alongside any Bible verse, or get a curated chain of verses for a doctrinal theme, ranked by scholarly and consensus sources.

Instructions

Retrieve the cross-references for a Bible reference — the passages traditionally read alongside it — or a curated chain of passages for a doctrinal theme.

Two modes:

By verse reference (most common). Pass reference="John 3:16" (or any canonical verse) to get the passages historically read alongside it. The database draws from four scholarly sources, returned in a three-tier ranking:

Tier 3 (top, "consensus and curated"): - CH — Harrison & Romhild's curated dataset (~58k links, OT-only as source). Hand-vetted; high-relevance pairs flagged canonical-direction. - Gage parallel — the tighter pairings from Warren Gage's John ↔ Revelation typological reading (Bradley/Gage, John/Rev only). - TSK ≥100 votes — TSK pairs with crowd-source consensus that strong are near-universal cross-references (top ~0.4% of TSK) and break through to compete with curated.

Tier 2 ("argued and acknowledged"): - Burnett — David A. Burnett's argued chain for the Gen 15:5 / Rom 4:18 "star-like seed" deification reading (JSPL 5.2, 2015). ~30 pairs. - Gage chiastic — the looser-typology sheet of Bradley/Gage (the source spreadsheet labels these "looser connections, just noting"). - TSK 20–99 votes — solid topical links acknowledged across commentaries (top ~5%).

Tier 1 (long-tail): TSK <20 votes — surface only when explicitly raising limit for exhaustive study.

Results typically include the texts the verse quotes, its fulfilment passages, contested parallel readings, and the later authors who picked the verse up.

By theme. Pass theme="atonement" (or salvation_by_grace, deity_of_christ, resurrection, holy_spirit, justification) to get a hand-curated chain of foundational passages for that doctrine — relevant for broad theological questions not anchored to a specific verse.

Coverage caveat. TSK is built on R.A. Torrey's 19th-century index, which catalogues topical/thematic connections — not necessarily direct quotations or verbal allusions. Consequence: a verse with few cross-refs here is NOT necessarily a verse with few biblical echoes. Famously, Revelation shows surprisingly few links to OT prophetic books even though it is saturated with OT symbolism, because Torrey indexed by subject and Revelation's subject is "apocalyptic". The CH dataset partly compensates (it leans toward NT-quotes-OT linking), so source="ch" may surface a quotation or allusion the topical index misses, as may find_similar_passages for verbal parallels.

Adaptive default — limit is a cap, not a target. Default limit=8. Rows are returned in tier-then-strength order, and tier-1 noise (low-vote TSK) is suppressed by default whenever the verse has at least 3 rows from tier 2+. So:

  • Signal-rich anchors return 6–8 strong refs spanning curated, scholarly, and consensus-TSK sources.

  • Signal-poor anchors return only what passes the bar; a short result set means the verse has few well-attested links, not that the query failed.

For the long tail, source="tsk" returns all TSK rows including tier 1, and min_strength=0 sets an explicit floor of zero. Either disables tier-1 suppression; both pair with a higher limit (20–30).

Interpreting the scores. Each row carries type (the dataset), relevance (its native strength signal), and where applicable a tsk_votes side-channel showing the TSK count for that pair. The scales differ by dataset:

TSK vote scale (full corpus distribution): ≥ 500 votes — extraordinary; near-universal cross-reference (top 0.01%, only 35 pairs) 100-499 — very strong; the link tradition reflexively makes (top 0.4%) 50-99 — strong; well-established parallel (top 1.3%) 20-49 — solid; real connection acknowledged across commentaries (top 5%) 10-19 — moderate; one of many recognised links (top 12%) 5-9 — weak; thematic stretch, use with caution (top 33%) 2-4 — very weak; mostly noise floor (62% of TSK) 0-1 — noise

CH (curated — all CH refs carry signal; the tag indicates weight): "canonical direction" (rel=3 or 2) — Harrison's flag for the canonical direction of the pair, often part of a thematic circle (top 78% of CH) no tag (rel=0) — present in CH but unflagged (still hand-curated)

Gage (John ↔ Revelation typology): relevance=3 ("parallel" tier) — tighter pairings from the parallel-reading of John 1 ↔ Revelation 1 relevance=1 ("chiastic" tier) — looser thematic echoes across the full John-Revelation chiasm; the source spreadsheet flags these as "looser connections, just noting" The note field carries the thematic tags + commentary + per-row attribution (Bradley vs Gage). Treat as canonical-typology, not topical.

Burnett (single-paper argued chain): All Burnett rows are at relevance=5 by convention — they're explicit claims from one scholar's published argument, not graded by strength. The note field carries the JSPL citation and which step of the argument the pair belongs to. They represent a single scholarly proposal rather than consensus.

A result whose strongest row has only 5–15 votes indicates a verse the topical index does not treat as a major thematic anchor — a materially weaker signal than a 200-vote parallel. For such verses source="ch" (Harrison's curated set, which leans toward NT-quotes-OT links) and find_similar_passages (verbal/semantic parallels Torrey did not index) cover different ground.

The source parameter restricts results to a single dataset — useful when CH alone gives too little coverage for an obscure verse, or when the dense TSK long-tail is wanted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoCap on rows returned (not a target). Default 8. The returned count may be smaller when the verse has fewer rows above the noise floor. Values of 20–30 combined with `source='tsk'` or `min_strength=0` return the long tail.
themeNoTheological theme. One of: salvation_by_grace, deity_of_christ, atonement, resurrection, holy_spirit, justification.
sourceNoOptional dataset filter when using `reference`. 'ch' = Harrison/Romhild curated; 'tsk' = Treasury of Scripture Knowledge; 'gage' = Gage/Bradley John↔Revelation typology; 'burnett' = Burnett's Gen 15:5 / Rom 4:18 deification chain (JSPL 5.2). Default: all four, ranked CH/Gage > Burnett > TSK.
referenceNoBible reference to find cross-references for (e.g. 'John 3:16', 'Rom 3:23').
min_strengthNoStrength floor for TSK refs (vote count). TSK pairs below this are excluded; CH/Gage/Burnett refs are exempt from this floor, being hand-curated or scholarly-argued. Setting this also disables the default tier-1 suppression, since it specifies an explicit floor. Sensible thresholds: 0 (include long-tail), 5 (drops bottom ~75%% of TSK), 20 (top ~5%% only). Default: tier-1 suppressed when verse is signal-rich.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds substantial behavioral context beyond them: tier rankings, suppression behavior, source-specific strength scales, scholarly provenance, and the meaning of short result sets. No text contradicts the annotations.

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

Conciseness4/5

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

The description is long but well-structured with bold headers, explicit modes, and front-loaded usage instructions. It is appropriately detailed for a complex multi-dataset tool, though the extensive tier and score-scale explanations push against strict conciseness.

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?

Given five optional parameters, no output schema, and a complex ranking system across four datasets, the description supplies all context needed to call the tool correctly and interpret its results. It covers modes, defaults, caveats, score scales, and alternatives in enough depth to prevent misuse.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema for all five parameters: limit is a cap not a target, min_strength sets a TSK floor and disables default suppression, source restricts to a dataset, theme selects curated doctrinal chains, and reference triggers the primary mode. It also explains how those parameters interact.

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?

The description states a precise verb+resource: retrieve cross-references for a Bible reference or a curated chain for a doctrinal theme. It distinguishes the two primary modes and names sibling/alternative tools such as find_similar_passages.

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?

It gives explicit guidance on when to use reference vs theme, when to restrict by source, when to raise limit or set min_strength to reveal the long tail, and when to prefer find_similar_passages or source='ch'. The coverage caveat and adaptive-default explanation remove ambiguity about result counts.

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