Skip to main content
Glama

Study notes for a chapter

get_chapter_study
Read-onlyIdempotent

Everything bible.flogvit.com has about one chapter: summary, historical context, key words, the people in it, themes, stories, prophecies, gospel parallels and timeline events. Give a chapter ("Rom 8"); verses are ignored.

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

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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the safety profile is covered. The description adds genuine behavioral detail beyond them: it discloses the full payload of sections returned and the non-obvious rule that verse-level portions of a reference are discarded. It does not mention depth limits or what happens for chapters with sparse content.

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 filler: a dense inventory of returned sections followed by the calling convention and its caveat. The essential behavior ('verses are ignored') is front-loaded in the same sentence as the example.

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 read-only, open-world-false tool with no output schema, the description needs to signal the shape of the response, and the section list does that well. It is only slightly short on what a caller gets when a chapter has little or no study content beyond the documented language fallback.

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%, and the mapping parameter's schema text already explains numbering differences in detail. The description contributes nothing about reference format beyond one example and nothing about mapping or 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-and-resource: everything the site has about one chapter, enumerated as summary, historical context, key words, people, themes, stories, prophecies, gospel parallels and timeline events. That content enumeration separates it from siblings like get_passage (raw text) or get_book_overview (whole book), though no sibling is named 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?

'Give a chapter ("Rom 8"); verses are ignored' gives a concrete input convention and a scope constraint, which is real usage guidance. But it never says when to prefer this over get_passage, get_book_overview, or the individual get_story/get_prophecies/get_timeline tools that clearly feed this aggregate.

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.