Skip to main content
Glama

Shprd Bible

Get the text of a Bible passage

get_bible_passage
Read-onlyIdempotent

Get the exact text of a Bible passage to quote or explain. Call this every time before you write Bible text in your reply, even a verse you know well: the WEB's wording differs from other translations (its John 3:16 says "only born Son"), so fetch the exact text instead of relying on memory. Use this when the user asks you to quote a passage or give the words in the conversation, or you need the exact text to answer a question, for example "John 3:16", "Psalm 23" or "1 Corinthians 13:4-7" in the World English Bible. Returns the exact verses with a WEB credit. Up to 200 verses per call; a longer range stops there and says how to continue. Do not use it to search by topic or words (use search_bible) or to get other translations. To read, open or show a passage, use open_bible_reader instead (in ChatGPT it shows a card).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reference": "<reference>"
    },
    "name": "get_bible_passage"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesBook, chapter and optional verses, e.g. "John 3:16", "John 3:16-18", "Psalm 23", "Romans 8:28-9:3", "Jude 5".

Output Schema

NameRequiredDescriptionDefault
bookYes
versesYes
referenceYes
truncatedYes
attributionYes
translationYes
nextReferenceNo
omittedVersesYesRequested verses that the WEB prints only in footnotes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, and the description adds substantive facts the annotations cannot: the translation-specific wording risk ('only born Son'), the 200-verse cap with truncation-and-continue behavior, and the attached WEB credit. That is real behavioral disclosure beyond structured fields.

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 purpose, then rationale, then usage, then exclusions, then limits and return shape — a sound ordering with no filler sentences. Slightly long and mildly repetitive ('even a verse you know well' restates the memory caveat), which keeps it off a 5.

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?

For a single-parameter read tool with an output schema, everything an agent needs is present: what it returns, the 200-verse ceiling and continuation path, translation identity, and routing to the correct sibling. Nothing material is missing.

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 coverage is 100% and the single 'reference' parameter already carries format examples ('John 3:16-18', 'Romans 8:28-9:3'), which the description largely repeats with chapter-only and cross-chapter examples. Baseline 3 applies since the schema does the heavy lifting; the description adds little syntax meaning beyond it.

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 ('Get the exact text of a Bible passage') and immediately scopes it against siblings: not search, not other translations, not the reader view. An agent can distinguish it from search_bible and open_bible_reader without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('when the user asks you to quote a passage or give the words'), an unusually strong precondition ('call this every time before you write Bible text'), and explicit when-not with named alternatives for topic search and for reading/showing passages.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources