Skip to main content
Glama

Get Bible Chapter

bible.text.passage
Read-onlyIdempotent

Fetch the verse-by-verse text of a Bible chapter by specifying translation, book, and chapter number. Returns an array of verse numbers and text.

Instructions

Fetch the verse-by-verse text of a Bible chapter for a given translation and book (e.g. KJV / John / 3). Returns array of {number, text}. Free Use Bible API

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
translationYesBible translation ID (e.g. "KJV", "ASV", "WEB", "BSB").
bookYesBook ID — typically a 3-letter code (e.g. "GEN", "JHN", "PSA") or full name. Use bible.books to discover.
chapterYesChapter number (1-based, e.g. 3 for John 3).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior3/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds no new behavioral traits beyond stating it's a 'Free Use Bible API'. No contradiction with annotations.

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-loads the purpose with no extraneous information. Every sentence serves a clear function.

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

Completeness5/5

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

Given the tool's simplicity, strong annotations, and mention of return format (array of {number, text}), the description is complete. No missing behavioral details needed for this read-only chapter fetch.

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% with adequate descriptions for each parameter. The description's example (KJV/John/3) adds marginal value beyond what the schema already provides.

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?

Description clearly states the tool fetches verse-by-verse text of a Bible chapter, specifying required inputs (translation, book, chapter) with an example. It distinguishes itself from sibling catalog tools that list books/translations.

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?

Description implies when to use this tool (to get Bible chapter text) but does not explicitly exclude alternatives or provide when-not guidance. However, sibling tool names (e.g., 'bible.catalog.books') make the distinction clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server