Skip to main content
Glama
djayatillake

Study Bible MCP Server

by djayatillake
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

find_similar_passages

Read-onlyIdempotent

Find Bible passages with semantically similar content to a given verse using vector embeddings, revealing thematic connections beyond keywords.

Instructions

Find passages with similar semantic content to a given Bible verse.

USE THIS to discover thematic connections across the Bible that may not be captured by explicit cross-references or shared vocabulary. This tool uses vector embeddings to find passages with similar meaning, not just similar words.

EXAMPLES OF DISCOVERIES:

  • Daniel 7:13-14 (Son of Man vision) → Revelation 1:7, 14:14 (similar imagery)

  • Exodus 12:1-13 (Passover) → John 1:29, 1 Corinthians 5:7 (Lamb imagery)

  • Isaiah 53:4-6 (Suffering Servant) → 1 Peter 2:24-25 (echoes of Isaiah)

  • Proverbs wisdom themes → James practical wisdom

⚠️ CRITICAL HERMENEUTICAL WARNING: Semantic similarity does NOT equal theological connection or relevance. Two passages may use similar language but have completely different meanings based on their literary context, historical setting, and authorial intent.

BEFORE USING SIMILAR PASSAGES IN YOUR RESPONSE, YOU MUST:

  1. Check Genre Compatibility: A prophetic vision and a historical narrative may share imagery but require different interpretive approaches. Use lookup_verse to understand each passage's genre.

  2. Verify Historical Context: What did this passage mean to its original audience? Similar language across centuries may have different referents.

  3. Examine Literary Context: Is the similar passage using the language literally, metaphorically, or as an allusion? A quote vs. independent usage matters greatly.

  4. Apply Fee & Stuart's Questions:

    • What did this text mean to the original readers?

    • What is the author's stated purpose?

    • How does this fit the book's overall argument/narrative?

  5. Distinguish Types of Similarity:

    • Direct quotation (explicit OT in NT)

    • Deliberate allusion (author intentionally echoing)

    • Shared tradition (common Jewish/Christian concepts)

    • Coincidental similarity (similar words, unrelated meaning)

Only present a similar passage as theologically relevant if you can establish an actual interpretive connection, not mere semantic overlap.

Takes a verse reference (with pre-computed embedding) and returns semantically similar passages ranked by similarity score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
referenceYesBible reference to find similar passages for (e.g., 'John 3:16', 'Daniel 7:13')
limitNoNumber of similar passages to return. Default: 10

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds significant behavioral context: it uses vector embeddings, returns ranked results, and crucially warns that semantic similarity does not imply theological connection, listing potential pitfalls.

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

Conciseness3/5

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

The description is well-structured and front-loaded with the main purpose, but it is verbose with multiple sections and lengthy bullet points. It could be more concise while retaining essential information.

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?

Despite lacking an output schema, the description explains it returns ranked passages by similarity score and provides ample context for an agent to use the results responsibly. It covers how to interpret and validate the output.

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

Parameters4/5

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

Schema coverage is 100%. The description adds context: reference is a Bible verse, limit is number (optional). It also mentions 'pre-computed embedding' for the reference, which provides additional nuance beyond the schema.

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 clearly states the tool's function: 'Find passages with similar semantic content to a given Bible verse' and distinguishes it from siblings like get_cross_references and search_lexicon by emphasizing vector embeddings for semantic meaning.

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?

Provides extensive when-to-use guidance, including examples of discoveries, a critical hermeneutical warning, and a detailed step-by-step checklist for responsibly using results. It implicitly tells when not to use (e.g., for exact quotes or explicit cross-references).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/djayatillake/studybible-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server