Skip to main content
Glama
Sign In

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

by bible.besorah
OverviewDiscussionsAdmin

A verse in its setting

get_context
Read-onlyIdempotent

Returns a verse in its setting in one call: the verses before and after (2 each by default, 0-8), the verse itself, or up to 5, word by word, and its cross-references, quotations and parallels. Combines several lookups into one answer. Use when the user asks what surrounds a verse, with its neighbouring verses and connections.

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

Input Schema

NameRequiredDescriptionDefault
afterNoverses after, 0-8, default 2
beforeNoverses before, 0-8, default 2
formatNooptional: json (default) or markdown (compact, readable)
editionNowhich text, e.g. septuagint, onkelos, pseudo-jonathan, jonathan, hebrew-nt, hebrew or greek
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'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / edition / description
      Added value: +"which text, e.g. septuagint, onkelos, pseudo-jonathan, jonathan, hebrew-nt, hebrew or greek"
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that — that this is an aggregating call bundling several lookups, and the default window sizes — but says nothing about response size limits, pagination, or what happens when a reference has no cross-references.

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, front-loaded with the payoff and then the trigger condition, with no filler. The phrase 'or up to 5, word by word' is slightly garbled and forces a re-read, which is the only real drag on structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters and no output schema, the description does the necessary work of describing returned content, which is a genuine strength. However it leaves the edition parameter — a major capability covering Septuagint and targum texts — and the max_chars truncation behavior entirely to the schema, so an agent could miss that this tool returns non-default textual witnesses.

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 every parameter is already documented, and the description mostly restates the before/after defaults and 0-8 range already in the schema. It adds no meaning for edition (septuagint, targum, etc.), format, or max_chars, which are the parameters most needing explanation.

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 names a specific verb and resource ('Returns a verse in its setting') and enumerates exactly what comes back: surrounding verses, the verse word-by-word, cross-references, quotations and parallels. 'Combines several lookups into one answer' distinguishes it from narrower siblings like get_cross_references or get_quotations, though no sibling is named directly.

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 a clear triggering condition: 'Use when the user asks what surrounds a verse, with its neighbouring verses and connections.' That tells the agent the right context, but it offers no explicit when-not guidance or named alternative for a user who only wants cross-references or a plain verse text.

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

All Besorah — the Bible in Hebrew, Greek, Aramaic and English toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources