Skip to main content
Glama
Sign In

FLOGVIT.bible

by io.github.flogvit
OverviewDiscussionsAdmin

A number in the Bible

get_number
Read-onlyIdempotent

What a number means in the Bible (e.g. 7, 12, 40, 666) and every passage where it carries that meaning. Called with no number, it lists every number that has an entry, with its meaning.

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

Input Schema

NameRequiredDescriptionDefault
numberNoThe number, e.g. 3, 7, 12, 40, 666, 1000. Default: none, which lists every number that has an entry.
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.
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, non-destructive, and closed-world. The description adds useful behavioral context by stating that calling without a number lists every available number with its meaning, and that returned results include passages carrying the meaning. It does not describe pagination or exact response shape, but the annotations lower the disclosure burden.

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, front-loaded with the core purpose and then the important no-argument behavior. No wasted wording.

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 read-only tool with no output schema, the description adequately explains the primary return content (meaning and passages) and the list-all fallback. The mapping and language effects are documented in the schema, so the remaining gap is minor.

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 all three parameters are already well documented. The description reinforces the no-number default behavior but does not add meaning beyond the schema for the number, mapping, or language parameters. Baseline 3 is appropriate.

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 description clearly identifies the resource (a biblical number) and what is returned (its meaning plus every passage carrying that meaning). It is specific enough to distinguish this from general Bible search or topic tools, though it does not explicitly name or contrast with any sibling tool.

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 by the description and by the no-number behavior, which explains how to list all available numbers. However, it gives no explicit guidance on when to use this tool versus siblings like search_bible or search_topics, and no exclusions are stated.

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