Skip to main content
Glama

Shprd Bible

List Bible books

list_bible_books
Read-onlyIdempotent

Use this when the user asks which books the Bible has, how many chapters a book has, or you need a book's canonical code or name. Lists all 66 books in canonical order with testament and chapter count. Do not use it to read text (use get_bible_passage).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bible_books"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
booksYes
attributionYes
translationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description does not need to restate safety. It does add scope details beyond the annotations: the list is a complete fixed set of 66 entries returned in canonical order and includes testament and chapter count, which tells the agent the result is exhaustive and stable. It does not describe response shape, but an output schema exists so that is not required.

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 short sentences: purpose and payload first, then use cases, then the exclusion. Every sentence carries distinct information and there is no redundant restatement of the title.

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 zero-parameter, read-only listing tool with an output schema and full annotation coverage, the description supplies everything needed to call it correctly. Triggers, exclusions, and the shape of the result set are all stated.

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

Parameters4/5

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

The tool takes zero parameters, so the schema carries no semantics to compensate for, and the baseline applies. The description correctly implies no arguments are needed to obtain the full canonical list.

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?

"Lists all 66 books in canonical order with testament and chapter count" gives a specific verb, a concrete resource, and the exact contents and ordering of the result. The final sentence names the sibling it is not (get_bible_passage), so an agent can separate it from the other Bible tools without opening a 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?

It gives three concrete trigger conditions (asking which books exist, chapter counts, or needing a canonical code/name) and an explicit exclusion with the alternative to use instead. Nothing about when to select this tool is left to inference.

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