Skip to main content
Glama
Sign In

FLOGVIT.bible

by io.github.flogvit
OverviewDiscussionsAdmin

List verse numberings

list_verse_mappings
Read-onlyIdempotent

The verse numberings (KVN mappings) the tools can read references in and number answers in, for the mapping argument of get_passage, get_original_text, get_cross_references, check_references and others. Bible editions number some verses differently — whether a psalm heading is a verse, where a chapter breaks — and a reference copied from one edition can point at another verse in the site's own numbering (osnb). Find the id by the edition's name or language, e.g. "king james", "dnb2024", "german", "swahili".

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": "list_verse_mappings"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords the id or the name must contain, e.g. "king james", "dnb", "nynorsk", "german", "spanish". Default: none, which lists the named numberings and then every id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond that: that results are ids keyed to a site numbering (osnb), that references copied from other editions may misalign, and that search can be by edition name or language. It does not describe result ordering or size, though the schema covers the default listing behavior.

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?

Three dense sentences, front-loaded with the resource and its consumer tools. The middle sentence on numbering differences is necessary motivation, though the closing example list is slightly repetitive with the schema examples.

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, but the description explains what the ids are for and how to locate one, which is what an agent needs before calling a one-optional-parameter lookup tool. What the response contains (id plus edition name) is only implied rather than stated, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning by saying the query matches the edition's name or language, which extends the schema's 'id or the name' wording with language-based search expectations and concrete multilingual examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('The verse numberings (KVN mappings)') and immediately explains what they are used for. It also distinguishes the tool from siblings by naming the consuming tools (get_passage, get_original_text, etc.) and their 'mapping' argument.

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?

Makes the when-to-use context explicit: call this to obtain an id for the mapping argument of several named tools. It also explains the motivating problem (editions numbering verses differently). It stops short of stating when not to use it or naming an alternative lookup tool such as list_editions.

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