Skip to main content
Glama

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

New Testament quotations

get_quotations
Read-onlyIdempotent

Returns where the New Testament quotes the Old, in either direction: give a New Testament book, chapter or verse for the Old Testament passages it quotes, or an Old Testament one for the New Testament passages that quote it. Each result carries both English texts and a link; 15 per page by default (limit 1-40, and nextOffset continues). Use when the user asks where the New Testament quotes the Old Testament, or the reverse.

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

Input Schema

NameRequiredDescriptionDefault
limitNohow many results to return (1-40, default 15)
formatNooptional: json (default) or markdown (compact, readable)
offsetNohow many results to skip; the previous answer's nextOffset is where its page ended
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. 'Matthew', 'Hebrews 1', 'Psalm 110:1', 'Isaiah 53'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"how many to return"New value: +"how many results to return (1-40, default 15)"
  2. Changed1 schema field changed
    • addedInput schema / properties / offset / description
      Added value: +"how many results to skip; the previous answer's nextOffset is where its page ended"
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), yet the description still adds real behavioral value: default page size of 15, a limit range of 1-40, and the fact that nextOffset continues the result set. It also discloses result content ('both English texts and a link'), which is useful since there is no output schema. No auth, rate-limit, or error behavior is mentioned, keeping it short of a 5.

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?

Two sentences with no filler; the core behavior and the usage condition are both front-loaded. The first sentence is dense and stacks clauses with dashes and parentheses, which slightly hurts scanability but does not waste words.

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 and five parameters, the description carries the burden of explaining return values, and it does name the payload (English texts plus a link) along with pagination and truncation mechanics. What is missing is minor: no note on ordering of results or on what happens when a reference yields no quotations.

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 the schema already documents limit, format, offset, max_chars, and reference with examples and defaults; the description mostly restates those numbers. What it does add beyond the schema is the reference semantics itself — that a New Testament reference yields the Old Testament passages quoted and vice versa — which the schema's terse examples do not convey. That extra meaning is modest, so baseline-plus-one is not warranted.

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?

The description uses a specific verb+resource pairing ('Returns where the New Testament quotes the Old') and makes the bidirectional scope explicit, so an agent knows exactly what data comes back. It does not name any sibling tool, so the differentiation from the similarly-named get_cross_references is left implicit rather than stated.

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 final sentence gives a concrete triggering condition: 'Use when the user asks where the New Testament quotes the Old Testament, or the reverse.' That is a clear usage context, but there are no exclusion rules or named alternatives for adjacent tools such as get_cross_references or get_related_passages.

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