GetBible MCP

Official

by getbible

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

List chapters in a book

list_chapters

Read-onlyIdempotent

Identify chapter numbers and hashes for a specified translation and book, providing the necessary identifiers before fetching scripture verses.

Instructions

Return chapter mappings and hashes; discover identifiers before retrieving scripture.

Input Schema

TableJSON Schema

Name	Required	Default
`book`	Yes
`api_version`	No	v3
`translation`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`cache`	No
`source`	Yes
`hash_guidance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedv2.1.1Sep 16, 2026

addedInput schema / properties / api_version

Added value: +{
+  "default": "v3",
+  "enum": [
+    "v2",
+    "v3"
+  ],
+  "title": "Api Version",
+  "type": "string"
+}

removedInput schema / properties / book / description
```
Removed value: -"GetBible book number."
```
removedInput schema / properties / book / maximum
```
Removed value: -200
```
removedInput schema / properties / translation / description
```
Removed value: -"Translation abbreviation, e.g. 'kjv'."
```

addedOutput schema / $defs / CacheAdvice

Added value: +{
+  "additionalProperties": false,
+  "description": "Consumer guidance only: this MCP never stores upstream responses.",
+  "properties": {
+    "cacheable": {
+      "title": "Cacheable",
+      "type": "boolean"
+    },
+    "expires_at": {
+      "format": "date-time",
+      "title": "Expires At",
+      "type": "string"
+    },
+    "hash_validation_required": {
+      "title": "Hash Validation Required",
+      "type": "boolean"
+    },
+    "max_retention_seconds": {
+      "default": 2592000,
+      "title": "Max Retention Seconds",
+      "type": "integer"
+    },
+    "policy": {
+      "title": "Policy",
+      "type": "string"
+    },
+    "recommended": {
+      "title": "Recommended",
+      "type": "boolean"
+    },
+    "remaining_ttl_seconds": {
+      "minimum": 0,
+      "title": "Remaining Ttl Seconds",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cacheable",
+    "recommended",
+    "remaining_ttl_seconds",
+    "expires_at",
+    "hash_validation_required",
+    "policy"
+  ],
+  "title": "CacheAdvice",
+  "type": "object"
+}

removedOutput schema / $defs / SourceInfo / properties / api_version / const
```
Removed value: -"v2"
```
removedOutput schema / $defs / SourceInfo / properties / api_version / default
```
Removed value: -"v2"
```
addedOutput schema / $defs / SourceInfo / properties / api_version / enum
```
Added value: +[
+  "v1",
+  "v2",
+  "v3"
+]
```

addedOutput schema / $defs / SourceInfo / properties / headers

Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "title": "Headers",
+  "type": "object"
+}

addedOutput schema / $defs / SourceInfo / properties / service

Added value: +{
+  "enum": [
+    "api",
+    "query",
+    "search",
+    "dictionaries",
+    "commentaries",
+    "bookmarks"
+  ],
+  "title": "Service",
+  "type": "string"
+}

addedOutput schema / $defs / SourceInfo / properties / status_code

Added value: +{
+  "default": 200,
+  "maximum": 599,
+  "minimum": 100,
+  "title": "Status Code",
+  "type": "integer"
+}

changedOutput schema / $defs / SourceInfo / required

Previous value: -[
-  "url",
-  "fetched_at"
-]New value: +[
+  "url",
+  "fetched_at",
+  "api_version",
+  "service"
+]

addedOutput schema / properties / cache

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/CacheAdvice"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedv1.0.0Aug 25, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds that it returns 'chapter mappings and hashes' and that it is for discovering identifiers, which is useful. It does not disclose details like pagination or whether hashes are content hashes, but with annotations covering the main behavioral traits, a 3 is appropriate.

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?

The description is a single sentence, front-loaded with the main action and result. It is concise and every word earns its place. It could be slightly more structured, but it is appropriately sized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return values are documented elsewhere. The description explains the purpose and the discovery workflow. However, with 0% parameter coverage and no mention of required parameters or how to use the output, an agent might not know what 'translation' and 'book' values are expected. The output schema helps, but the description is incomplete for a tool with 3 params and no param docs.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It mentions 'translation' and 'book' implicitly via 'in a book' but does not explain the meaning of 'translation', 'book', or 'api_version'. The description adds no parameter-level detail beyond the schema's field names and types. With 0% coverage and 3 params, this is a significant gap.

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 states a specific verb ('Return') and resource ('chapter mappings and hashes'), and the title clarifies it lists chapters in a book. It does not explicitly differentiate from siblings like list_books or get_scripture, but the mention of 'discover identifiers before retrieving scripture' gives some context. It is clear enough but not a full sibling differentiation.

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?

The description implies usage: use this to discover identifiers before retrieving scripture, which is a clear context. It does not explicitly name alternatives or exclusions, but the phrase 'before retrieving scripture' signals when to use it. Given the sibling list includes get_scripture and query_verses, this is adequate but not explicit.

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

Deploy Server