Skip to main content
Glama

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

Connections between books

get_book_connections
Read-onlyIdempotent

Returns the chapters a book, or one chapter, is most connected to elsewhere in the Bible: chapter pairs joined by at least two verse-level cross-references (OpenBible.info), most-linked first, each with its link count and a link. 15 by default (limit 1-40). Use when the user asks which chapters a book or chapter is most connected to.

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_book_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNohow many results to return (1-40, default 15)
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)
referenceYesa book ('Isaiah') or a chapter ('Psalm 22')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"how many results to return"New value: +"how many results to return (1-40, default 15)"
  2. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"how many results to return"
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent, closed read, so the description is not carrying the safety burden. It still adds real context beyond them: the provenance ('OpenBible.info'), the threshold that defines a connection, most-linked-first ordering, and the 'each with its link count and a link' result shape. What is missing is any note on what happens for a book with few or no qualifying pairs, or how pagination interacts with the default.

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 core behaviour is front-loaded in a single dense sentence, with the usage trigger at the end. Every clause carries information, though the first sentence is heavily loaded with parentheticals and could be split for easier scanning.

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?

With no output schema, the description compensates by naming the return fields (link count, link) and the ordering. Combined with the fully documented parameters, an agent has enough to call this correctly; only edge-case behaviour for sparse books is left unstated, which is minor for a read-only lookup.

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 coverage is 100%, so the schema already defines limit, format, max_chars and reference with the same details. The description restates the default and cap (15 by default, limit 1-40) but adds no new syntax or format meaning. Baseline 3 is appropriate where structured fields do the heavy lifting.

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 specific verb and resource ('Returns the chapters a book, or one chapter, is most connected to elsewhere in the Bible') and pins down the exact inclusion criterion (chapter pairs joined by at least two verse-level cross-references), the data source, and the sort order. That is enough to separate it from a plain cross-reference lookup without opening a schema.

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?

It gives an explicit trigger: 'Use when the user asks which chapters a book or chapter is most connected to.' That is clear context for invocation. It stops short of exclusions or alternatives, though the sibling set contains near-neighbours such as get_targum_connections or get_cross_references that a short contrast clause could have ruled in or out.

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