Skip to main content
Glama

Besorah — the Bible in Hebrew, Greek, Aramaic and English

Related passages

get_related_passages
Read-onlyIdempotent

Returns the verses connected to one verse, grouped by kind: voted cross-references, quotations in either direction between books, curated parallel passages, and similar wording. Use when the user asks what passages are related to one verse.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reference": "<reference>"
    },
    "name": "get_related_passages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many results to return
formatNooptional: json (default) or markdown (compact, readable)
max_charsNooptional: cap the answer at about this many characters (lists are shortened and marked truncated; use offset/nextOffset to get the rest)
referenceYese.g. 'John 3:16', 'Psalm 23', 'Genesis 1:1-3', '1 Corinthians 13:4-7'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"how many results to return"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already carry readOnly, idempotent, non-destructive, and closed-world hints, so the bar is lower. The description still adds real value by disclosing that results are grouped by kind and that cross-references are "voted" (i.e., community-ranked) while quotations run in either direction between books. It does not mention result ordering or default limits, which would have pushed it higher.

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: the return shape first, the trigger condition second. No filler, no restating of the title, and the most decision-relevant information (the four categories) is front-loaded.

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?

There is no output schema, but the description compensates by explaining that results come back grouped by kind across four categories, which is enough for an agent to interpret the response. The only gap is that pagination and truncation behavior lives in the schema rather than the description, and the schema's mention of offset/nextOffset has no corresponding parameter.

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 limit, format, max_chars, and reference are all documented in the schema with examples. The description adds no additional parameter meaning, so the baseline of 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?

Specific verb and resource ("returns the verses connected to one verse") plus an enumeration of the four result categories (voted cross-references, bidirectional quotations, curated parallels, similar wording). This makes clear it is an aggregate view, which implicitly separates it from narrower siblings like get_cross_references and get_quotations, though it never names them outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use when the user asks what passages are related to one verse" gives a usable trigger condition, but there is no guidance on when to prefer the narrow siblings (get_cross_references, get_quotations, get_context) over this combined tool, and no exclusions. Adequate but leaves the routing decision to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources