Skip to main content
Glama

Cross-references

get_cross_references
Read-onlyIdempotent

Other passages that relate to each verse of a passage, with a short note on how. Read them with get_passage (several references in one call, separated by ";").

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

NameRequiredDescriptionDefault
mappingNoVerse numbering to read the reference in and to number the answer in: a mapping id from list_verse_mappings, e.g. "english_kj" (King James), "dnb2024_nb" (Bibelselskapet 2024), or a short name such as "kjv" or "dnb2024". Numberings differ where a psalm heading is a verse or not, and at chapter breaks: Malachi 4:5 in the King James numbering is Malachi 3:23 in osnb. Default: osnb, the site's own numbering, which follows the Hebrew and Greek.
languageNoLanguage for names, notes and study content, and for the links to bible.flogvit.com: en (English), nb (Norwegian Bokmål), nn (Norwegian Nynorsk), sv (Swedish), fr (French), es (Spanish), fi (Finnish), de (German). Content missing in a language falls back to English. Default: en.en
referenceYesBible reference in English or Norwegian style, e.g. "John 3:16", "Joh 3,16-18", "1 Cor 13:4-7", "Ps 23", "Gen 1:1-2:3". Several separated by ";": "Rom 8:28; 9:1; John 3:16".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Language for names, notes and study content: en, nb (Norwegian Bokmål), nn (Norwegian Nynorsk), sv, fr, es, fi, de. Content missing in a language falls back to English."New value: +"Language for names, notes and study content, and for the links to bible.flogvit.com: en (English), nb (Norwegian Bokmål), nn (Norwegian Nynorsk), sv (Swedish), fr (French), es (Spanish), fi (Finnish), de (German). Content missing in a language falls back to English. Default: en."
    • addedInput schema / properties / mapping
      Added value: +{
      +  "description": "Verse numbering to read the reference in and to number the answer in: a mapping id from list_verse_mappings, e.g. \"english_kj\" (King James), \"dnb2024_nb\" (Bibelselskapet 2024), or a short name such as \"kjv\" or \"dnb2024\". Numberings differ where a psalm heading is a verse or not, and at chapter breaks: Malachi 4:5 in the King James numbering is Malachi 3:23 in osnb. Default: osnb, the site's own numbering, which follows the Hebrew and Greek.",
      +  "minLength": 2,
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds that results carry explanatory notes and can be batched into get_passage, but says nothing about coverage limits, whether every verse has references, or the volume of results — useful for a lookup that may return empty sets.

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 with zero filler and the core capability front-loaded; the follow-up sentence adds actionable chaining advice. Minor ambiguity in the pronoun 'them' (references vs. notes), but overall efficient.

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 three-parameter, fully documented lookup with no output schema, the description covers what is returned (related passages plus explanatory notes) and how to use it downstream. It lacks only result-volume/empty-result expectations, which is a minor gap given the rich schema.

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 coverage is 100% and the enum/descriptions for mapping, language and reference are thorough. The description only restates the semicolon-multi-reference convention already documented in the schema, adding no new parameter semantics. Baseline 3 applies when the schema carries the burden.

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 first sentence names the resource precisely (cross-references per verse) and adds the distinctive payload — a short note explaining the relationship. It's clear what the tool returns, though it never explicitly contrasts itself with near-siblings like get_gospel_parallels or get_chapter_study.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives useful downstream usage guidance ('Read them with get_passage', semicolon-separated multi-reference form), which tells the agent how to consume the output. However, it never states when to choose this tool over the other reference-related siblings (check_references, get_gospel_parallels), so the selection guidance is only implied.

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.