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

Cross-references

get_cross_references

Read-onlyIdempotent

Returns the voted cross-references (OpenBible.info) of one verse, each with its reference and link; the first few also carry their English text. 12 by default (limit 1-30). Use when the user asks for the cross-references of one verse.

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

Input Schema

Name	Required	Description
`limit`	No	how many results to return (1-30, default 12)
`format`	No	optional: json (default) or markdown (compact, readable)
`max_chars`	No	optional: cap the answer at about this many characters (lists are shortened and marked truncated; use offset/nextOffset to get the rest)
`reference`	Yes	e.g. 'John 3:16', 'Psalm 23', 'Genesis 1:1-3', '1 Corinthians 13:4-7'

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 12, 2026

changedInput schema / properties / limit / description

Previous value: -"1-30, default 12"New value: +"how many results to return (1-30, default 12)"

First observedNov 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: the data source (OpenBible.info, community-voted ranking), the per-result fields, and the fact that only the first few results include English text — a useful output-shape disclosure. It does not mention truncation behavior or the offset/nextOffset continuation referenced in the schema.

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 tight sentences, front-loaded with what is returned and followed by the usage trigger — no filler. The only minor waste is repeating the default limit and range that the schema already states.

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?

For a simple single-verse lookup with no output schema, the description covers return contents (reference, link, partial English text), source, and default result count — enough for an agent to call it and interpret the response. Only the truncation/continuation mechanics, which live in the schema, are left unaddressed in prose.

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's '12 by default (limit 1-30)' only restates the limit schema text. It adds no meaning for the format enum or max_chars/truncation behavior, so the baseline 3 is appropriate.

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?

States a specific verb and resource — 'Returns the voted cross-references (OpenBible.info) of one verse' — and even describes the payload (reference, link, English text for the first few). The source attribution and 'voted' qualifier distinguish it from generic passage tools, though it never names a sibling such as get_related_passages to draw the line explicitly.

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?

'Use when the user asks for the cross-references of one verse' gives a clear, concrete trigger condition, including the single-verse scope constraint. It offers no when-not guidance and does not say how it differs from adjacent tools like get_related_passages or get_quotations, so it stops short of full routing guidance.

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 tools Inspect

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

Need Help?