Skip to main content
Glama

Besorah — the Bible in Hebrew, Greek, Aramaic and English

List the books

list_books
Read-onlyIdempotent

Returns every book with its code, chapter count, the editions it exists in and its URL, and the list of editions. The whole list comes back in one piece. Use when the user asks what books, editions or book codes are available.

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_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNooptional: json (default) or markdown (compact, readable)
max_charsNooptional: cap the answer at about this many characters (lists are shortened and marked truncated; use offset/nextOffset to get the rest)

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, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds 'The whole list comes back in one piece', which usefully signals single-response retrieval, but it does not reconcile that with the max_chars truncation behavior documented only in the schema, nor mention size expectations.

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?

Two sentences, front-loaded with the return contents before the usage trigger. 'The editions it exists in and its URL, and the list of editions' is slightly redundant, mildly blurring the field list.

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 no output schema, the description carries the return-shape burden and does so by naming the fields returned. For a two-optional-parameter list tool this is nearly sufficient; only response size/truncation interaction is left implicit.

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 both parameters (format, max_chars) are documented with their own descriptions, so the schema does the heavy lifting. The description adds nothing about either parameter, which is acceptable at baseline 3.

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 (returns every book) and enumerates the returned fields: code, chapter count, editions, URL. Scope ('every book') is explicit enough to separate it from per-book siblings like get_book_connections or compare_books.

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?

Gives a concrete trigger: 'Use when the user asks what books, editions or book codes are available.' There is no exclusion clause naming an alternative tool for the filtered/compared cases, but the usage context is clear.

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