Skip to main content
Glama

Hebrew or Greek source text

get_original_text
Read-onlyIdempotent

The Hebrew (Old Testament, Leningrad Codex) or Greek (New Testament, SBLGNT) text of a passage, optionally word by word with an explanation of each word. The word explanations are written in Norwegian; translate them for the user when needed.

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

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".
word_by_wordNotrue lists every word with pronunciation and explanation (at most 20 verses); false gives the text alone (at most 200 verses). Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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"
      +}
    • addedInput schema / properties / word_by_word / description
      Added value: +"true lists every word with pronunciation and explanation (at most 20 verses); false gives the text alone (at most 200 verses). Default: true."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is that word explanations come out in Norwegian and should be translated, plus the underlying source editions. Useful operational context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero padding, with the core resource stated first and the Norwegian-translation caveat second. Every clause earns its place.

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?

No output schema exists, and the description sketches the return shape (plain text vs. per-word entries with pronunciation and explanation) and language behavior. Slightly short on pagination/limits, but those are carried by the schema's verse caps.

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%, with mapping, language, reference and word_by_word all fully documented including defaults and examples. The description adds essentially nothing parameter-specific beyond the word-by-word explanation language, so baseline 3 applies.

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-like resource: the Hebrew (Leningrad Codex) or Greek (SBLGNT) text of a passage, optionally word by word with explanations. This clearly separates it from translation-oriented siblings like get_passage, though it never names an alternative explicitly.

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?

Usage is implied rather than spelled out: the agent infers this is the tool for original-language text, and the Norwegian-explanation note gives handling guidance. There is no explicit when-to-use/when-not or comparison to get_passage or search_original_word.

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.