Skip to main content
Glama

Shprd Bible

Read a Bible passage in the Shprd reader

open_bible_reader
Read-onlyIdempotent

Read a Bible passage or chapter from the World English Bible. Use this when the user asks to read, open, show or look up a passage, for example "read Romans 8", "open Matthew 9" or "show me Psalm 23". In ChatGPT the passage appears in a reader card with previous and next chapter buttons and the source credit, and the verse text is not returned to you (use get_bible_passage when you need the words yourself or the user asks for them in the chat). In hosts that cannot show the card, it returns the passage text. Do not use it to search by words (use search_bible).

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
referenceYes
attributionYes
translationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior the annotations cannot express: in ChatGPT the text is NOT returned to the agent and appears only in a reader card, while hosts without card support return the text. Minor gap: no mention of error behavior for an unresolvable reference.

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?

Three sentences, each doing distinct work: what it does, when to call it with examples, and the host-dependent return behavior plus the exclusion. The most surprising fact (verse text not returned in ChatGPT) is stated before the alternatives so the agent cannot mis-plan its next step.

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?

The tool is simple (one parameter), an output schema exists, and annotations cover the safety profile, so the description needs only to explain triggers and the host-dependent return path, both of which it does. Nothing an agent needs in order to call it correctly 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?

With a single required parameter and 100% schema description coverage, including format examples like "John 3:16-18" and "Romans 8:28-9:3", the schema already carries the parameter semantics. The description adds no reference-syntax guidance beyond it, so the baseline of 3 is appropriate.

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 ('Read a Bible passage or chapter from the World English Bible') and immediately scopes it with concrete triggers like "read Romans 8" and "show me Psalm 23". An agent can distinguish this from get_bible_passage and search_bible 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?

Explicitly names the conditions that select this tool (read/open/show/look up a passage) and the conditions that rule it out: use get_bible_passage when the words are needed in chat, and search_bible when searching by words. Both alternatives are tied to a concrete user-intent trigger.

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