Skip to main content
Glama

who_read_verse

Find who on the shelf (Church Fathers, rabbis, mystics, reformers, commentators, philosophers) quotes a given Bible verse, with the quotation and a link. So far only 42 well-known verses are indexed (Genesis 1:1, Psalm 23:1, Isaiah 53:5, John 1:1, John 3:16, Romans 1:17 ...); "indexed": false means the verse is not on that list, not that nobody quotes it.

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": {
      "ref": "<ref>"
    },
    "name": "who_read_verse"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesA single verse, e.g. "MAT.5.39" or "John 1:1"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose the critical behavioral caveat: partial index coverage and the exact meaning of the 'indexed': false flag. It stops short of describing ordering, pagination, or how many authors might be returned, which matters for a lookup that could return long lists.

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 core capability, followed by the caveat that most affects correct interpretation. The parenthetical author categories are somewhat long but they do real work by telling the agent who is being indexed.

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 does sketch the return payload (quotation, link, 'indexed' flag) and warns about the narrow index, which is the key completeness risk for this tool. Ordering and result-volume behavior remain unstated, but nothing essential for calling 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?

Schema description coverage is 100% on the single 'ref' parameter, and the schema already supplies both example formats ('MAT.5.39' and 'John 1:1'). The description adds no format, normalization, or validation guidance beyond what the schema states, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: 'Find who ... quotes a given Bible verse', names the kinds of authors returned, and states that results include the quotation and a link. It is unmistakably an inverse-lookup tool, but it never names or contrasts a sibling such as get_passage, so the differentiator is implicit rather than stated.

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?

It clearly establishes the operating envelope: only 42 well-known verses are indexed, with examples, and it spells out that 'indexed': false means the verse is absent from the index rather than that no one quotes it. That prevents the most likely misuse, but there is no explicit routing to an alternative tool when a verse is not indexed (e.g., use get_passage instead).

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