Skip to main content
Glama

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

Questions and their answers

list_questions
Read-onlyIdempotent

Returns pairs of passages in which a question asked in one place is answered in another (e.g. 'what is man?' in Job and Psalm 8). Each pair has its theme, the asking and answering passages, and a note. theme (god, man, suffering, sin, death, time, wisdom, worship, messiah) or contains narrows the list; unfiltered, every pair comes back in one large piece. Use when the user asks about a question in one passage that another passage answers.

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

Input Schema

NameRequiredDescriptionDefault
themeNotheme id: god, man, suffering, sin, death, time, wisdom, worship or messiah
formatNooptional: json (default) or markdown (compact, readable)
containsNoonly questions whose text contains this word
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. Changed2 schema fields changed
    • addedInput schema / properties / contains / description
      Added value: +"only questions whose text contains this word"
    • addedInput schema / properties / theme / description
      Added value: +"theme id: god, man, suffering, sin, death, time, wisdom, worship or messiah"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover safety (readOnly, idempotent, closed-world), so the description's extra context is what counts: it discloses the payload shape (theme, both passages, note) and warns that unfiltered calls return every pair 'in one large piece.' It doesn't restate truncation/offset mechanics for max_chars, leaving that to the schema, keeping it at 4 rather than 5.

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 concrete example, then payload shape, then filtering behavior, then when to use. Slightly dense with parenthetical asides, but no sentence is filler.

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-required-param, read-only list tool with full schema coverage, this covers the concept, the return shape, filter effects, the unfiltered-volume caveat, and the usage trigger. No output schema exists, yet the pair structure is described well enough to interpret results.

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%, so the baseline is 3. The description reinforces that theme/contains narrow the list and that no filter means the full set, but adds no syntax or value hints beyond the schema's own enum list and field descriptions.

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 question/answer passage pairs, with a concrete example ('what is man?' in Job answered in Psalm 8). It also enumerates the payload of each pair (theme, asking passage, answering passage, note), which no sibling tool (get_cross_references, compare_books) claims.

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?

Explicit trigger: 'Use when the user asks about a question in one passage that another passage answers.' That gives clear conditions for selection without naming an exclusion against a specific sibling, so it stops short of a 5.

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