Skip to main content
Glama

get_torah_weave

Read-onlyIdempotent

Retrieve structurally-paired verses for any Torah passage to uncover deliberate interwoven parallels across Genesis through Deuteronomy.

Instructions

Get the structurally-paired verses for a Torah passage under Moshe Kline's Woven Torah hypothesis.

The Torah is organised as 86 two-dimensional literary units (Genesis–Deuteronomy). Each unit is a grid of cells arranged in rows and columns, and cells are deliberately paired with one another across rows (horizontal partners) and down columns (vertical partners). Knowing the weave partners of a verse gives you additional passages that the Torah's author(s) intended to be read alongside it.

USE THIS when:

  • Studying any passage in Genesis, Exodus, Leviticus, Numbers, or Deuteronomy

  • You want to see which other verses are structurally paired with a passage

  • You suspect two passages in the Torah are deliberately interwoven (doublets, creation/flood, law parallels, etc.)

  • You're preparing a comparative reading and want the author-intended partners, not just thematic cross-references

  • You want additional context for a Torah verse beyond lexical or thematic similarity

WHAT IT RETURNS:

  • The literary unit the verse sits in (title, format, type, verse span)

  • The cell the verse occupies (row/column label + verse range)

  • Horizontal partner cells (same row, same subdivision, different column)

  • Vertical partner cells (same column, same subdivision, different row)

  • Sibling cells (same row and column, adjacent subdivisions)

  • A short explanation of what each direction of pairing means under Kline's method

  • A directive block instructing the caller how to turn these pointers into an interpretation

HOW TO USE THE OUTPUT: This tool returns STRUCTURAL POINTERS, not pre-written interpretation. After calling it, call lookup_verse on each partner cell's verse range to read the actual text, then synthesise the interpretation yourself using the directional semantics the tool provides. Horizontal partners are symmetric parallels (same register, different thematic tracks); vertical partners trace a progression through divine-name registers along a single thematic track. Reading the paired verses and applying those semantics is how the weave yields meaning.

Only Torah books (Genesis through Deuteronomy) have weave data. Source: Moshe Kline, chaver.com, CC BY 4.0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
referenceYesBible reference in Genesis–Deuteronomy (e.g., 'Genesis 6:1', 'Exodus 14:21', 'Leviticus 19:18')
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the tool returns structural pointers, not pre-written interpretation, and explains the output semantics (horizontal/vertical/sibling partners, directional meaning). It also mentions the source and provides a directive block for using the output. No contradictions.

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 description is structured into clear sections: purpose, background, use cases, output description, how to use, limitations. Every sentence adds value, and the key purpose is front-loaded. It is slightly long but appropriate for the specialized nature of the tool.

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?

Given the complexity of the tool and no output schema, the description adequately explains what is returned (unit, cell, partners, explanations) and how to use the output (call lookup_verse on partners, synthesize interpretation). It also cites the source and method, making it sufficiently complete.

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% with one required parameter 'reference'. The description adds meaning by specifying 'Bible reference in Genesis–Deuteronomy' and providing examples, as well as the domain constraint (only Torah books). This adds value beyond the schema description.

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 purpose: 'Get the structurally-paired verses for a Torah passage under Moshe Kline's Woven Torah hypothesis.' It specifies the verb (Get), resource (structurally-paired verses), and domain (Torah passage, specific hypothesis). The use cases list further clarifies, and it distinguishes from siblings like get_cross_references by focusing on structural pairing.

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 description includes a 'USE THIS when:' section listing specific scenarios, and it notes that only Torah books have data, implying a limitation. It doesn't explicitly mention when not to use or name alternatives, but the context distinguishes it from thematic 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