Skip to main content
Glama

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

Targum connections

get_targum_connections
Read-onlyIdempotent

Returns the curated list of places where the Targumim (the Aramaic translations of the Torah and Isaiah) and the New Testament share an idea, phrase or contrast. Each entry has a title, whether it is a shared idea or a contrast, the Targum passages, the New Testament passages, and a note saying what is and is not claimed. The whole list comes back in one piece; it takes no filter. Use when the user asks where Targum wording and the New Testament overlap.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_targum_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add payload and caveat detail — which it does by describing the 'what is and is not claimed' note and the curated (not computed) nature of the list. However, 'The whole list comes back in one piece; it takes no filter' is misleading next to the max_chars parameter, which the schema says shortens and truncates lists with an offset/nextOffset continuation. That internal tension blurs how the tool actually behaves.

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?

Payload contents and the use case are front-loaded, and the sentences are free of filler. The clause 'The whole list comes back in one piece; it takes no filter' is partially redundant with what follows and, as noted, inaccurate regarding truncation.

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 carries the return-shape burden and does so by listing every entry field, including the epistemic caveat note. What is missing is any mention of the markdown/json format choice or the truncation/offset behavior that the schema exposes, which matters for an agent retrieving a long list.

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 format and max_chars are already fully documented, and the baseline of 3 applies. The description adds nothing about either parameter and in fact implies there are no controls at all ('takes no filter'), leaving the schema to do all the work.

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 concrete verb and resource ('Returns the curated list of places where the Targumim ... and the New Testament share an idea') and enumerates the payload fields (title, shared idea vs contrast, Targum passages, NT passages, note). The scope is unmistakable. It stops short of naming a sibling such as get_cross_references or get_quotations that an agent might confuse it with, so it earns a 4 rather than a 5.

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 where Targum wording and the New Testament overlap.' That is clear context for selection. There are no exclusions or named alternatives, so an agent comparing it against get_cross_references or get_quotations gets no routing help.

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