Skip to main content
Glama
Sign In

FLOGVIT.bible

by io.github.flogvit
OverviewDiscussionsAdmin

The Bible timeline

get_timeline
Read-onlyIdempotent

Events in the order they happened, with year, description and the passages they are told in: for a period ("the exile"), a span of years, or events that mention a person or place. Called with no arguments, it lists the periods with their years. Years before Christ are negative. The world timeline gives what happened in the world around at the same time.

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords the event's title or description must contain, e.g. a person ("David", "Paul") or a place ("Babylon"). Default: none.
periodNoA period, by id or by words from its name, e.g. "exodus", "exile", "Jesus' life", "early church". Call with no arguments to see them all. Default: none.
mappingNoVerse numbering to give the verse references in: a mapping id from list_verse_mappings, e.g. "english_kj" (King James) or "dnb2024_nb", or a short name such as "kjv". Default: osnb, the site's own numbering.
to_yearNoLast year to include; negative is BC, e.g. -900. Default: no upper limit.
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
timelineNobible (the events the Bible tells) or world (world history in the same periods). Default: bible.bible
from_yearNoFirst year to include; negative is BC, e.g. -1000 for 1000 BC. Default: no lower limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/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, so the safety profile is covered. The description adds genuine behavior not in the annotations: the no-argument call returns a period index rather than events, BC years are negative, and a parallel 'world' timeline exists for contemporaneous history. It says nothing about result-size limits or pagination, which is the remaining gap.

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?

Front-loaded with the return shape before the query modes, and each sentence carries information. The final sentence about the world timeline sits slightly awkwardly after the parameter guidance and could be folded into the mode list.

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 seven all-optional parameters and no output schema, the description usefully names the returned fields and both the default and no-argument behaviors. What is missing is any sense of result volume or limits, which matters for a tool that can be called with no filters at all.

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 including mapping, language and year bounds is already documented in the schema. The description's contributions (negative-year convention, period examples, no-args listing) largely restate schema text, so this lands at the baseline.

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 resource (timeline events) and the returned fields (year, description, passages, in chronological order), so an agent knows exactly what it gets back. It does not differentiate itself from nearby siblings like get_person, search_bible or get_passage, which a reader must infer from the domain terms alone.

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 enumerates the query modes (a named period, a year span, or a person/place mention) and notes that no-argument calls list the available periods, which is real usage framing. However, it never says when to reach for this tool instead of get_person, search_bible or get_passage, so the routing decision is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FLOGVIT.bible toolsInspect
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