Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

Bible

Bible
Read-only

Bible: Bible retrieves scripture passages and verses across nine public-domain translations, including the modern Berean Standard Bible (BSB), KJV, ASV, YLT and Darby. Look up a book, chapter and verse range or a written reference like Jn 3:16-18, search for words and phrases, get a random verse or the verse of the day, and step to the previous or next passage. (Cost: 1 credit)

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": {
      "version": "<version>"
    },
    "name": "Bible"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNoThe name of the book in the bible (e.g., Genesis). Abbreviations such as Gen, Ps, 1 Cor or Jn are accepted
dateNoDate to get the verse for (YYYY-MM-DD). Defaults to today (UTC)
pageNoPage of results, 20 per page
queryNoWords to find (all must appear, whole words, any case); wrap a phrase in double quotes to match it exactly
verseNoThe verse number in the chapter
chapterNoThe chapter number in the book
versionYesThe Bible translation version
verseEndNoLast verse of a range starting at verse (e.g., verse=16&verseEnd=18). A value past the end of the chapter returns the rest of it
referenceNoA Bible reference: book (full name or abbreviation), chapter, and optional verses, ranges and comma-separated lists
testamentNoLimit the random verse to the Old (OT) or New (NT) Testament

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context via the 'Cost: 1 credit' note and the translation licensing scope, but says nothing about rate limits, response size, or what makes it open-world.

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 the resource and translation scope, then a compact capability list, with the cost note trailing in parentheses where it is easy to scan. The second sentence is long and comma-chained but every clause names a distinct capability, so little is wasted.

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?

With an output schema present, return values need no explanation, and the description covers modes, translations, accepted reference syntax and cost. The one loose end is 'step to the previous or next passage', which has no obvious corresponding parameter in the schema, leaving the mechanism unexplained.

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 every parameter is already documented, including abbreviation handling, quote-wrapped phrase matching and verseEnd overflow behavior. The description's mode list hints at which parameters belong together but never states the mapping explicitly, so it adds only marginal meaning over the schema.

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 ('retrieves scripture passages and verses') and quantifies scope ('nine public-domain translations'), naming BSB, KJV, ASV, YLT and Darby. It also enumerates the supported modes, so an agent knows this single tool covers reference lookup, keyword search, random verse, verse of the day and passage stepping.

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 second sentence maps capabilities to situations ('look up a book, chapter and verse range', 'search for words and phrases', 'get a random verse'), giving clear context for each mode. It stops short of stating prerequisites or which parameter combination triggers which mode, and there are no exclusions, so it lands just below the top.

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

All APIVerve 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